analyze-audio-waveform

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

No annotations provided, so description carries full burden. It discloses that uncompressed PCM WAV is read natively, other formats are transcoded via ffmpeg if installed, and mentions the AE_FFMPEG_PATH env var override. Also describes return values: normalized amplitude values (0-1) and peak times.

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?

Three sentences with clear front-loading of purpose. The second sentence is instructional but not verbose. Could be slightly more structured, but overall concise with no wasted words.

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?

Given no output schema and no annotations, the description comprehensively covers dependencies, format handling, env var, and output structure. Addresses all needed context for agent to invoke 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 coverage is 100%, so baseline is 3. The description adds context: filePath should come from get-audio-info, numPoints default is 200 and max 100000. It also explains return values beyond schema, but the schema already covers parameter details well.

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 the tool analyzes audio to extract waveform amplitude data and detect peaks/transients. The verb 'analyze' paired with resource 'audio-waveform' is specific and distinguishes it from sibling tools like set-audio-levels or add-any-effect.

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?

Explicitly instructs to first call get-audio-info to obtain the sourceFilePath, then pass it here. Also details format handling (WAV native, others need ffmpeg) and env var override, providing clear when-to-use guidance.

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