get_clip_pitch

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Get the pitch shift' without describing the return value (e.g., units), error handling, or side effects. While 'get' implies read-only, the description does not add meaningful behavioral context beyond the tool's name and action.

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 concise and front-loaded, with the purpose stated in the first sentence and parameters listed clearly. Every word serves a purpose, and there is no redundancy or fluff.

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 basic purpose and parameter meanings. However, it lacks usage guidance, return format, and error behavior, which are important for an agent to invoke it correctly. The omission is not fatal but leaves clear gaps.

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 description coverage is 0%, so the description must compensate. However, the parameter descriptions ('The index of the track', 'The index of the clip slot') mostly restate the parameter names. The only minor addition is 'clip slot', which clarifies the clip_index refers to a slot, but overall the semantic value is minimal.

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 'get' and a specific resource 'audio clip' with the attribute 'pitch shift', clearly distinguishing it from siblings like get_clip_gain and get_clip_warp_info. The purpose is immediately apparent.

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 on when to use this tool instead of alternatives. The description does not mention any context, prerequisites, or exclusions. It simply states the action and parameters.

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