Call tracking: call audio recording

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

Discloses response format (structured binary with mimeType, sizeBytes, base64), decoding requirement, file size, and error handling (HTTP 425). Annotations already indicate read-only, but description adds significant operational context.

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, front-loaded with main action. Each sentence adds value: what it does, how to process response, and when it's available. No wasted words.

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?

Given no output schema, description fully explains response format, error case, and limitations. Annotations cover safety. All necessary information is present.

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?

Only one parameter (callId) with 100% schema coverage. Description adds the context that it's the call identifier, but the schema already provides this. Baseline 3 applies since schema covers parameter meaning.

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 'Downloads the call-tracking conversation audio recording for a specific callId (read-only)'. Distinguishes from calltracking_get_call_by_id and calltracking_get_calls, which are explicitly mentioned as alternatives.

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 specifies when to use this tool (for audio) and when to use alternatives (calltracking_get_call_by_id for metadata, calltracking_get_calls for list). Also notes delay and retention, guiding proper invocation.

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