transport_set_playback_speed

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

With no annotations, the description must disclose behavioral traits. It mentions the range (0.25..4.0) but does not explain side effects like pitch change, tempo independence, or whether it affects recording. Essential transparency is missing.

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 a single sentence of 36 characters with no filler, achieving maximal conciseness while conveying the core purpose and constraint.

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?

For a straightforward setter with one parameter, the description is largely complete. However, it omits return value (no output schema) and any behavioral context. Still adequate for its simplicity.

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 schema provides only type 'number' for the 'speed' parameter, with 0% coverage. The description adds the valid range '0.25..4.0' and implies it's a multiplier, significantly improving understanding beyond the bare 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 what the tool does: 'Set the playback speed multiplier (0.25..4.0).' It uses a specific verb ('Set') and resource ('playback speed multiplier'), and distinguishes itself from sibling tools like transport_play, transport_set_tempo, etc.

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?

No guidance is provided on when to use this tool versus alternatives, such as transport_set_tempo or transport_tap_tempo. The description lacks prerequisites, context, or exclusions.

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