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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only a hint at what is returned ('waveform metadata', 'audio channels') and says nothing about behavior for missing/expired recordings or the size/shape of the payload, which matters since there is no output schema.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity comes at the cost of the missing usage and return-shape context noted elsewhere.

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?

The tool is simple (one required parameter) and annotations cover safety, but with no output schema the description should say more about what 'waveform metadata' actually contains (sample counts, peaks, duration, channel list). As written it names the return surface without describing it.

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 the single 'id' parameter is already documented with pattern, length bounds and provenance. The description adds nothing beyond the schema – notably it never states that the id is a recording id, leaving the agent to infer the identifier's domain from the tool name.

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 pairs a specific verb ('Read') with a concrete resource ('recording waveform metadata and available audio channels'), which is more informative than a bare 'get'. It does not, however, distinguish itself from the other get_*/list_* siblings (e.g. get_metrics, list_calls) or clarify that this is scoped to recordings.

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?

Usage is only implied by the resource name – an agent can infer 'call this when you need waveform metadata for a recording'. There is no explicit when-to-use, no prerequisites, and no mention of alternatives such as list_calls or other recording-related tools.

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