get_conversation_audio_route

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without the description. The description's real addition is the return MIME type (audio/mpeg), which matters because there is no output schema, plus the save-vs-inline behavior; however it says nothing about size limits, permissions, or persistence. Useful but not rich.

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?

Very short and front-loads the core action before the output_path note. It is slightly marred by a run-on construction ('Get Conversation Audio Returns audio/mpeg bytes') that reads as two merged sentences, costing a point on structure.

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?

With only two fully-described parameters, no output schema, and annotations covering the safety profile, the description supplies the one thing structured fields do not: the returned content type. What remains missing is return-size or error behavior, which keeps it from a 5.

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 are already fully documented in the schema, including the ELEVENLABS_OUTPUT_DIR resolution and base64-inline fallback. The description's 'pass output_path to save them' repeats the schema's meaning without adding new semantics; 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 ('Get') and resource ('Conversation Audio') and adds the return type ('audio/mpeg bytes'), so the agent knows what it retrieves and in what form. It does not differentiate itself from adjacent sibling tools like get_conversation_signed_link or get_audio_full_from_speech_history_item, so it stops short of a 5.

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?

There is no when-to-use guidance, no mention of prerequisites or auth, and no pointer to alternative retrieval tools. The only usage hint is the mechanical 'pass output_path to save them', which is invocation detail rather than selection guidance.

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