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

Annotations already declare read-only/idempotent/non-destructive, but the description goes well beyond them: size cap (32 KB), rate limit (60 RPM), statelessness, demo mode, L402 payment of 75 sats, and HTTP 400 on invalid input. That is exactly the operational context an agent needs before calling.

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?

The core purpose and the sibling routing are front-loaded in the first two sentences. The final sentence is a dense run-on packing budget, rate limit, defaults, demo/L402 and error behavior, which is efficient but slightly overloaded for one clause chain.

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?

An output schema exists, so return values need not be explained, and the description still covers scope, selection criteria, limits, auth/payment, and error behavior. Nothing material for correct invocation is missing.

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?

Schema description coverage is 100%, so both parameters and the enum are already documented. The description restates 'input' and the response_tone default without adding format or syntax guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Processes real-time conversational dialog turns') plus the differentiating capabilities (acoustic emotion, interruption handling, paralinguistic cues). It explicitly names the sibling synthesize_gemini_speech_audio and the boundary between them, so an agent can route correctly without opening either schema.

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?

Gives an explicit when-to-use ('interactive voice-agent dialog turns that require tone and turn-taking awareness') and a when-not-to-use with the alternative and its condition ('one-way text-to-speech readout of a static text string → synthesize_gemini_speech_audio'). Nothing is left to inference.

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