transport_set_playrate

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

No annotations are provided, and the description only states 'Set playback speed' without disclosing side effects, reversibility, or whether it affects pitch. The behavioral context is minimal beyond the tool name.

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 extremely concise at two lines, with no wasted words. It is front-loaded with the purpose and immediately provides parameter details.

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 low complexity and single parameter, the description is minimally sufficient. However, it lacks information about return values, whether it works during playback or only when stopped, and any potential impact on pitch or other settings.

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 adds significant meaning to the sole parameter 'rate' by specifying a valid range (0.25-4.0) and the default meaning (1.0=normal), which the input schema does not provide.

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 'Set playback speed' with the verb 'Set' and resource 'playback speed', and provides the rate range. It distinguishes from sibling transport tools which focus on play/pause/record/tempo, not speed.

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 implies usage for adjusting playback speed, but does not explicitly state when to use it versus alternatives like transport_set_bpm or transport_play, nor does it mention any prerequisites or context (e.g., while playing or stopped).

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