a2a_send

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Mentions immediate return and rejection when not your turn, but does not describe side effects, idempotency, or whether it modifies state. Since annotations are absent, more behavioral detail would be helpful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no redundancy. Directly explains action, precondition, and postcondition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the key usage pattern with wait_turn, the rejection condition, and the immediate return. Lacks details about return value and error handling, but overall sufficient for a simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter 'message' is described as a reply, giving some semantic meaning, but no format, length, or content constraints are provided. Schema has no description, so the description carries a light burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool submits a reply to the current pending turn, and references the wait_turn flow. No ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to call a2a_wait_turn first to see the prompt, and to call it again for the next turn. Also notes rejection when it's not your turn, providing clear usage boundaries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.