apply_tempo_map

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is covered. The description adds genuine but cryptic context: the remote object model cannot accept the GUI confirmation Live's Arrangement import requires, so import should go on a muted MIDI track. That is useful, but it never states what the apply operation actually destroys or how the destructive write is scoped.

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 text is short but structurally poor: a disjointed first sentence followed by three terse fragments with no clear flow, and the key action is not front-loaded. Most sentences carry some content, so it is not padded, but the readability cost is real.

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?

An output schema exists, so return values need not be explained, and the muted-track workaround is a helpful addition for a complex Arrangement-import scenario. Even so, for a destructive tempo-application tool the description leaves the core mechanism and its distinction from sibling tempo tools under-specified.

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%; both parameters (confirm, analysis_path) are documented in the schema, including that confirm=false previews without Live writes. The description adds nothing about either parameter, so the baseline of 3 applies.

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 name and first line suggest applying a reviewed tempo map, but the description muddles it by pairing 'apply a constant map through set_tempo' with 'explain Arrangement import for changes' as if two unrelated behaviors share one tool. An agent can infer the general intent from the name but the description itself does not cleanly state verb+resource or distinguish it from write_tempo_map/set_tempo.

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 implies a constant-vs-variable split (constant via set_tempo, variable exported as tempo-map.mid and handled through Arrangement import), which is implicit usage guidance. However it never explicitly states when to choose this tool over siblings like write_tempo_map, verify_tempo_map, or import_arrangement_audio, and the phrasing is ambiguous about whether set_tempo is invoked or recommended.

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