midi_insert_cc

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

No annotations exist, so description shoulders full burden. It only describes parameters and action, lacking behavioral details like effect on existing CCs, error conditions, or mutation scope.

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 purposeful sentences plus concise parameter list. Every element earns its place, delivering maximum information with minimal 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?

Covers all parameters with clear ranges and units. Lacks output/error details but acceptable for a straightforward insertion tool; very close to fully complete.

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 has 0% coverage; description compensates fully by explaining each parameter's range and unit (0-based track, 0-127 values, seconds for position), adding critical semantic value.

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 clearly states 'Insert single CC event' and explicitly names alternatives (cc_curves, rewrite_cc) for composing, distinguishing this tool from 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?

Provides explicit context: for single CC insertion vs. composing with curves. Does not include when-not-to-use scenarios, but gives clear directional guidance.

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