Get audio clip

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

Reveals key behaviors beyond schema: saves to local file (side effect), max 60s duration, and rate limiting. No contradictions with annotations (none provided).

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?

Two concise sentences, front-loaded with action and key details. No extraneous information.

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?

Covers all essential aspects: what it does, input constraints, output (file path), use case, and rate limit. No output schema needed; description adequately explains return value.

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?

Adds the 60-second maximum duration constraint not present in schema, though schema already describes parameters. High schema coverage (100%) reduces burden but extra constraint is valuable.

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 cutting a native-audio snippet and saving to a file, specifying the source (submission) and output (file path). Differentiates from sibling tool 'get_audio_url' which returns a URL.

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?

Provides a specific use case (embedding audio in HTML lessons) and implicit guidance that clips are small and rate-limited. Does not explicitly exclude alternatives like get_audio_url.

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