CPA: call recording (v1, deprecated)

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

Description adds 'Read-only, spends no money', which aligns with annotations (readOnlyHint, destructiveHint) but provides additional context. Rate limit is also disclosed. No contradiction with annotations.

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?

Four short sentences, front-loaded with purpose, then deprecation and alternatives, then rate limit. No unnecessary 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?

For a simple read-only deprecated tool with thorough annotations and schema, the description covers all necessary aspects: purpose, deprecation, alternatives, rate limit. Output is implicitly the audio recording, which is sufficient.

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 (call_id) is described in the description with source information ('obtained from cpa_get_calls_by_time_v2 or from a chat/action'), adding value beyond the schema's type and constraints. Schema coverage is 100%.

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?

Description clearly states 'Returns the recording (audio) of a CPA call by its identifier (v1, deprecated)'. It distinguishes from siblings by naming alternatives (cpa_get_call_by_id_v2, calltracking_get_record_by_call_id) and specifying that v1 is deprecated.

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 states deprecation and advises to prefer v2 or calltracking versions. Also notes rate limit (1 req/min). Provides clear when-to-use and when-not-to-use guidance.

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