set_clip_pitch

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

No annotations are provided, so the description must disclose side effects. It only states the action without mentioning whether the change is persistent, undoable, or requires specific track states, leaving the agent unaware of any mutation consequences beyond the direct assignment.

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 plus a compact argument list. Each line earns its place with no filler or redundant restatement of the tool name, making it appropriately sized and front-loaded.

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 simple setter, the description covers the purpose, all parameters, and ranges. However, it omits usage context such as whether the clip must be in the session view and any validations that might occur, leaving minor gaps that an output schema may or may not fill.

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 details every parameter with meaning and valid ranges (zero-based indices, coarse -48–48 semitones, fine -50–50 cents), fully compensating for the 0% schema description coverage and adding value beyond the bare schema properties.

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 uses a specific verb ('Set') and resource ('pitch transposition of an audio clip'), clearly stating what the tool does. It distinguishes from sibling clip modifiers like set_clip_gain or set_clip_warping by focusing on pitch transposition.

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 provides no guidance on when to use this tool versus alternatives. It neither explains prerequisites (e.g., clip must be in session view) nor contrasts with other set_clip_* tools, leaving the agent without context for selection.

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