get_audio_full_from_speech_history_item

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. The description adds the concrete return format (audio/mpeg bytes) and the inline-vs-saved behavior, which is useful context not present in the annotations, but it omits any mention of size limits, auth needs, or pagination. Adequate 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?

A single sentence that front-loads the purpose and then the output mechanism. It is efficient, though the run-on phrasing ('Get Audio From History Item Returns audio/mpeg bytes') is slightly grammatically awkward.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does so by naming the MIME type (audio/mpeg) and the inline-vs-file behavior. For a simple two-parameter binary fetch this is largely sufficient, though the relationship to sibling download tools remains unaddressed.

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 (history_item_id and output_path) are already fully documented in the schema, including the ELEVENLABS_OUTPUT_DIR resolution and base64 fallback. The description repeats output_path's role without adding syntax beyond the schema, so 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?

The description names a specific verb (Get) and resource (audio from a speech history item) and states the return type (audio/mpeg bytes). It does not, however, distinguish itself from closely related siblings like download_speech_history_items or get_speech_history_item_by_id, leaving the agent to infer the boundary.

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?

Only implied usage is present: it notes that passing output_path saves the bytes, which hints at a write-to-disk workflow. There is no statement of when to use this over alternatives like download_speech_history_items, and no prerequisites are given.

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