analyze_stems

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

The description discloses the operation is heavy and lists generated artifacts, but with no annotations, it provides limited behavioral detail such as idempotency, failure modes, or prerequisites.

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 concise, well-structured with a clear header, bullet points for generated files, and a usage guidance sentence, all without redundancy.

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?

The description covers purpose, generated artifacts, and usage context, but lacks prerequisite information or potential side effects on previously generated analysis.

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?

With zero parameters, the description adds meaning about the scope (all tracks) and the generated files, which is sufficient and goes beyond the schema.

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 clearly states the tool triggers deep audio analysis generating specific file types (summaries, spectrograms, analysis) for all tracks, distinguishing it from the read-only and parameter-setting siblings.

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 explicitly tells when to use (after recording or effect changes) and labels it a heavy operation, but does not mention when not to use or alternatives.

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