analyze_harmony

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

Description reveals beyond readOnlyHint=true: it filters drum tracks, uses music21, always returns confidence+alternatives, and hedges on non-chordal material. No contradiction.

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 sentences, front-loaded with purpose. Second sentence adds essential behavioral traits. No redundant 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?

With no parameters, annotations present, and output schema, the description covers all relevant behavioral aspects: filtering, algorithm, return type, and edge cases.

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?

No parameters, so baseline 4. Description adds context about what the tool does but no need for parameter-level details.

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?

Description starts with 'Detect key/scale/chords/Roman numerals/cadences' which is a specific verb and resource. It clearly distinguishes from sibling tools like analyze_audio_character or analyze_groove.

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?

Description explains when to use (for harmonic analysis) and what to expect (confidence+alternatives, hedging on non-chordal). Does not explicitly state when not to use or name alternatives, but context is clear.

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