get_clip_pitch

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention return value units, side effects, or error conditions. The statement 'Get the pitch shift' is minimal and leaves the agent uncertain about the nature of the returned data.

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 compact and well-structured: a clear one-sentence purpose followed by a simple parameter list. No unnecessary words or redundant details, making it easy to parse.

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 getter with two parameters, the description covers the action and parameter names but omits expected return format (e.g., semitones as a float) and any potential errors. While the tool is straightforward, the lack of an output schema means the description should have specified the return value to be fully complete.

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 only tautological phrases like 'The index of the track' and 'The index of the clip slot,' which barely extend the parameter names. It does not clarify zero-based indexing, valid ranges, or how the parameters relate, providing insufficient compensation for the schema's 0% description coverage.

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's function: 'Get the pitch shift of an audio clip.' It uses a specific verb and resource, and the name 'get_clip_pitch' aligns perfectly. This distinguishes it from sibling tools like set_clip_pitch or get_clip_gain.

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 set_clip_pitch. The description only states what it does without any context on selection, exclusions, or prerequisites.

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