set_arrangement_overdub

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

With no annotations, the description carries full burden and clearly discloses that enabling causes recorded notes to merge rather than replace. It does not discuss reversibility or permissions, but the primary effect is transparently stated.

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 compact and front-loaded with the main action, followed by a single clarifying sentence and the parameter documentation. Every sentence earns its place with no fluff.

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 1-parameter setter with an output schema, the description fully covers purpose, behavior, and parameter meaning. There is no missing context needed for an agent to invoke it correctly.

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 schema only provides a boolean with no description, so the Args block adds value by explicitly stating True enables and False disables. It also connects the parameter to the recording behavior described above.

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 'Set' and the resource 'arrangement overdub state', making it distinct from sibling tools like get_arrangement_overdub. The added sentence about merging notes explains exactly what the state controls, further differentiating it.

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 explains the behavioral consequence of enabling overdub (merging new notes with existing content), giving users the context needed to decide when to use it. It doesn't explicitly name alternatives or exclusions, but for a simple setter this is sufficient.

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