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

Annotations already mark the operation as read-only and non-destructive. The description adds meaningful context beyond those annotations: it specifies the required whatsapp_calls:read permission and clarifies that the result includes transcript/recording availability without claiming to return the content itself.

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 description is compact and front-loaded: it states the core purpose, the distinctive return information, and the required permission in two short clauses without any filler.

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?

For a simple single-ID read with an output schema and annotations available, the description covers the auth requirement and the key distinguishing detail about transcript/recording availability. It could explicitly point to sibling download/transcript tools, but nothing essential is missing for correct invocation.

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 0%, so the description carries the burden of explaining the parameter. It references the call ID but does not define its format, origin, or how it relates to the returned availability. Since there is only one required callId parameter and the verb 'get' makes its role fairly inferable, this is minimally adequate.

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?

The description names a specific operation (retrieve) on a specific resource (a single internal WhatsApp call) and notes that it returns transcript/recording availability. It is clear enough to be told apart from list_whatsapp_calls and get_whatsapp_call_transcript, though it does not explicitly distinguish itself from get_call.

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?

It provides a useful usage signal by stating the required permission and implying this is a lightweight read for checking availability. However, it does not explicitly say when to use this tool instead of get_call, get_whatsapp_call_transcript, or download_whatsapp_call_recording, so the guidance is implied rather than direct.

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