mcp_opendaw_create_tempo_ramp

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

With no annotations, the description fully explains the mechanism: it adds a series of tempo change events via ValueEventBox, describes interpolation behavior, and mentions return data. The no-op example adds useful behavioral insight. However, it doesn't disclose potential side effects such as interaction with existing tempo events or whether the operation is reversible.

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 well-organized, starting with a clear purpose, followed by parameter explanations, return info, and three illustrative examples. Every section adds value, and the examples are particularly informative. Although long, it is appropriately sized for a tool with this complexity.

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 covers all six parameters, provides usage examples, describes the return value, and places the tool in a musical context. The presence of an output schema means detailed return structure isn't required, making this description complete for correct selection and invocation.

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 description thoroughly explains every parameter: start_beat, end_beat, start_bpm, end_bpm with ranges, curve options with meanings, and steps with default and effect. This fully compensates for the 0% schema description coverage.

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 opens with a clear, specific action: 'Create a smooth tempo ramp (ritardando or accelerando) across a beat range.' It also distinguishes itself from add_tempo_change by stating it creates multiple events for a smooth curve, making the tool's unique purpose explicit.

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 strong usage context by naming musical scenarios (ritardando, accelerando) and includes three examples covering different use cases including a no-op. It differentiates from add_tempo_change by explaining the multi-event mechanism, but it doesn't explicitly state when not to use this tool or formally recommend alternatives beyond the implicit contrast.

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