🎼 Enhanced MIDI Send Note with Superior Audio Hearing

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'automatic musical expression' and 'real-time spectral/temporal/pitch analysis,' which suggest additional processing beyond basic MIDI sending, but lacks details on permissions, rate limits, or specific behavioral traits like error handling. It adds some context but leaves gaps for a mutation tool.

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 front-loaded with key information in two concise sentences, efficiently conveying purpose and differentiation. However, the use of emojis and marketing language ('Superior Audio Hearing') slightly detracts from clarity, though it remains overall well-structured.

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 annotations and no output schema, the description provides adequate context for a mutation tool with enhanced features but lacks details on return values, error conditions, or specific behavioral constraints. It covers the 'what' and 'why' but not the full operational context needed for robust use.

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 100%, providing comprehensive parameter documentation. The description does not add meaning beyond the schema, as it focuses on tool capabilities rather than parameter details. Baseline score of 3 is appropriate since the schema handles parameter semantics adequately.

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 specific action ('Send MIDI note') with enhanced capabilities ('automatic musical expression, real-time spectral/temporal/pitch analysis, and superior audio feedback'), and explicitly distinguishes it from a sibling tool ('REPLACES basic midi_send_note'). This provides a verb+resource+scope combination that differentiates it from alternatives.

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 explicit guidance on when to use this tool versus alternatives by stating 'REPLACES basic midi_send_note with enhanced capabilities,' indicating this should be used instead of a basic version. It also implies usage context through 'enhanced capabilities' for scenarios needing advanced features.

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