take_set_playrate

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

No annotations provided, but description fully discloses behavior: time-stretch effect with pitch preservation, speed change without pitch preservation, and that item length does not auto-resize. No contradictions.

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?

Description is concise and front-loaded with purpose. Uses clear bullet-style for args. Minor redundancy but overall efficient.

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 complexity (3 params, no output schema, 40+ siblings), description is complete. Explains effect, post-conditions (length not resized), parameter details, and usage scenarios. No need for more.

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?

Schema coverage is 0%, so description must explain all parameters. It does: item_index (global 0-based), rate (playback rate with range 0.05-16.0 and examples), preserve_pitch (default True, effect explained). Adds meaning beyond 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?

Clearly states 'Time-stretch a take by changing its playrate.' Distinguishes from siblings like transport_set_playrate, take_set_pitch, and take_set_reversed by specifying the behavior and use cases (fitting chop to beat grid, vinyl-style speed change).

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?

Explicitly tells when to use (fitting chop to beat grid, vinyl-style) and what not to expect: 'item's visible length does NOT auto-resize. Call item_set_length afterwards.' This guides the agent to use another tool after, providing clear context for usage.

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