mcp_opendaw_add_tempo_change

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

No annotations provided, but the description discloses the underlying mechanism (normalized values, automatic mapping from BPM), interpolation behavior, and that it returns the created tempo event and full tempo map. It does not mention side effects or destructive actions, but the tool's purpose is clear.

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 multiple sentences but each provides essential information: purpose, mechanism, parameter descriptions, return value. It is well-structured and front-loaded, though slightly verbose but not wasteful.

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?

Given the tool's complexity (3 required params, no enums, no annotations, no schema descriptions), the description covers all necessary aspects: what it does, how it works internally, parameter meanings, and output. It is complete for an agent to use 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?

With 0% schema description coverage, the description fully compensates by explaining all three parameters: position_beats (position in beats), bpm (target BPM 60-240), interpolation (linear/hold). It adds constraints, examples, and context beyond the schema.

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 tool adds a tempo (BPM) change at a specific position in the track. It explains the creation of ValueEventBox on the tempo track for mid-track automation, distinguishing it from other tempo-related tools like set_bpm or create_tempo_ramp.

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 provides clear usage context: adding BPM changes mid-track with examples (e.g., 120→90→140). It explains automatic conversion and interpolation types but does not explicitly contrast with alternatives like set_bpm or create_tempo_ramp, though the sibling list implies these exist.

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