ramp_parameter

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the ramp blocks execution, is undoable, or requires permissions. The existence of an output schema is noted but not described, leaving the return value ambiguous.

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: one sentence for purpose followed by a parameter list. Every sentence adds value and the structure front-loads the key action. No unnecessary text.

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 parameters and gives usage examples, but lacks behavioral context (e.g., real-time vs. scheduled, interruptibility, prerequisites like device existence). The output schema is not described, though its presence reduces the need for return value details.

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 schema description coverage at 0%, the description compensates by listing all parameters with clear, one-line explanations (e.g., 'track_index: 0-based'). This adds meaning beyond the schema's type and title, though some parameters like bpm and steps_per_beat have defaults explained.

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 smoothly ramps a device parameter over beats with examples like filter sweeps and reverb builds. This distinguishes it from sibling tools like set_device_parameter (immediate) and ramp_volume (volume-specific).

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 gives usage examples but does not explicitly contrast with alternatives like set_device_parameter or ramp_volume. It lacks guidance on when not to use this tool, relying on the user to infer from context.

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