channel_trigger_note

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

With no annotations, the description carries the full burden of disclosure. It states the action is a 'one-shot' and 'not recorded', hinting at non-destructive behavior. However, it lacks details on side effects, required state (e.g., channel selection), or whether the note is audible immediately. The behavioral context is basic but not fully transparent.

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 a single sentence that front-loads the essential verb and domain ('trigger a one-shot MIDI note'). No extraneous words or redundancy. Every word contributes to the core meaning.

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 the tool has four parameters and no output schema or annotations, the description is insufficient. It does not explain return behavior, error conditions, or dependencies (e.g., whether the channel must be specific). The completeness is inadequate for an agent to reliably invoke the tool without trial and error.

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 0%, yet the description provides no additional meaning for the four parameters (index, note, velocity, duration_ms). It only mentions 'MIDI note' generically. With no parameter elaboration, the description fails to add value beyond the schema names for an agent to correctly set arguments.

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 verb 'trigger', the resource 'one-shot MIDI note', and the scope 'on the channel (live preview, not recorded)'. It effectively distinguishes this tool from siblings like 'audio_analyze' or 'piano_roll_add_notes' which handle permanent or recorded data.

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 phrase 'live preview, not recorded' implies the tool is for real-time auditioning, not permanent changes. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. Some guidance is present but not comprehensive.

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