apply_midi_transposition

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

Annotations only signal non-read-only and non-destructive; the description adds that the operation is guarded and performs complete native readback verification after applying. It does not detail failure or conflict behavior, but it provides meaningful 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?

One front-loaded sentence contains purpose, scope, guard condition, and verification guarantee. There is no filler or repetition of schema details.

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?

The description complements a rich schema by stating the guarded plan/apply flow and verification, and the schema itself explains dryRun, planHash, and confirmationToken. However, with no output schema, it leaves the plan and readback result structure unspecified.

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%, so each parameter's meaning and constraints are already documented. The description adds no per-parameter elaboration and only lightly contextualizes the plan/apply workflow.

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 names the specific operation (MIDI transposition), its chromatic scope, and its guarded plan/apply nature. 'Chromatic' and 'complete native readback verification' separate it from diatonic and plan-only sibling tools.

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?

It conveys that the tool both plans and executes, and 'chromatic' implies the non-diatonic case, but it does not explicitly name alternative tools or state when not to use it. Usage context is inferable rather than clearly stated.

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