Summary

To be discussed, I think this name makes more sense because the A2A using the ADK is not only doing A2A protocol, internally it can use MCP or even standard Tool-Use. While it's true that externally it's using the A2A protocol to communicate the name is too specific.

I would like to rename it to Agent and Agents in plural so then it's possible to run:

kubectl get agents

And it will list for you all the agents.

IDK, doing something like:

kubectl get a2as

Feels not natural, A2A is implementation details.