set_arrangement_overdub

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

The description reveals the key behavioral trait: layering vs replacing. Annotations declare destructiveHint=false, which aligns. Adds useful context beyond annotations.

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?

A single, 14-word sentence that front-loads the purpose and effect. No unnecessary words, highly efficient.

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?

For a simple toggle with one parameter and an output schema, the description covers the essential function completely. No gaps given the tool's simplicity.

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?

Only one parameter 'enabled' (boolean) with 0% schema description coverage. While the param is self-explanatory, the description does not add any additional meaning or syntax guidance. Adequate but no value added.

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 'toggle' and the resource 'arrangement overdub', and explains the effect: layering MIDI onto existing clips instead of replacing. This distinguishes it from siblings like 'set_record_mode' or 'set_session_record'.

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 implies usage for layering MIDI recording but does not explicitly contrast with other recording modes or provide when/not guidance. No alternatives are mentioned.

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