ramp_volume

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

With no annotations, the description must fully disclose behavior. It explains the ramp concept but omits details like whether it overwrites existing automation, what happens if start_volume equals end_volume, and the exact role of steps_per_beat.

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 concise and front-loaded with the purpose. The parameter list is efficient, though it somewhat duplicates schema fields; the added details warrant the length.

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?

While the description covers basic usage, it lacks details on output (despite an output schema), interaction with existing track state, and precise interpolation behavior. More depth would improve completeness for this gradual automation tool.

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 provides ranges for start and end volumes and defaults for bpm and steps_per_beat, compensating for 0% schema coverage. However, it could clarify steps_per_beat more thoroughly.

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 ramps track volume smoothly over beats, specifying usage like fade-ins and fade-outs. This distinguishes it from instant volume tools like set_track_volume and generic ramp_parameter.

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 mentions use cases (fade-ins, fade-outs, dynamic changes) but does not explicitly exclude alternative tools like set_track_volume for instant adjustments, nor compare with siblings ramp_parameter or ramp_send.

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