analyze_audio_file

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

Beyond the readOnlyHint annotation, the description discloses no upload, no file modification, no normalization, partial-result marking for truncated analysis, and the caveat that decoding compressed files does not recover lost audio. This is exemplary behavioral context.

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?

The description is dense but efficient: supported formats and measured metrics come first, followed by limits, caveats, and safety guarantees. Every sentence adds meaningful information with no filler.

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 an output schema available, return-value documentation is already covered. Description addresses input requirements, analysis scope, safety behavior, and known limitations. An agent has enough context to decide when and how to call this tool correctly.

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 0%, so the description carries the parameter documentation burden. It explains max_seconds thoroughly: default 30, maximum 120, only the first segment analyzed, and partial results marked. It also clarifies that 'path' refers to a local file path, though it never names the parameter directly.

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 opens with a strong verb, 'Measure', and specifies the exact resource: local audio files in named formats with a precise set of metrics. The phrase 'without Live' helps differentiate it from in-session analysis tools like analyze_mix.

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?

The description clearly scopes when the tool applies: local files, certain formats, and a max_seconds window. However, it does not explicitly name alternatives or state when NOT to use this tool, such as pointing to analyze_mix for live session analysis.

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