assist_harmonic_overview

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

The description explains it runs across every MIDI clip, implying a batch read-only operation. Without annotations, it adds value by disclosing scope and operations, though it omits potential performance impacts 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?

Two short, front-loaded sentences that efficiently convey the tool's purpose and usage context without unnecessary 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?

While the description covers the tool's overall function and context, it lacks explanation of the required 'path' parameter and does not mention output or side effects. The presence of an output schema mitigates some gaps.

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?

The only parameter 'path' has no description and 0% schema coverage. The description does not explain what the path refers to (likely the project file), leaving the agent to guess.

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 runs key estimation and chord guessing across every MIDI clip in the set, distinguishing it from sibling tools that operate on single clips or individual analyses.

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 provides a clear use case ('where am I harmonically' overview) but does not explicitly exclude when not to use it or mention alternative tools for single-clip analysis.

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