set_clip_pan

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

No annotations are provided, yet the description only restates the operation. It does not disclose whether this mutates the clip, what units or value ranges are expected, whether it affects audio or video, or whether any selection is required.

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 short and front-loaded, but the 'Premiere Pro expanded operation:' prefix is generic filler that adds no real information. The substantive content is essentially the tool name, making it under-specified rather than effectively concise.

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?

With no annotations, no output schema, and a free-form input schema, this description must supply all context but does not. It omits what input the tool expects, what entity it operates on, and how an agent should invoke it correctly.

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 defines zero parameters and reports 100% coverage, so the baseline is 4. The description adds no parameter details, but with no formal parameters there is little to document; however, the free-form additionalProperties allows arbitrary input with no guidance.

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 names a specific verb and resource: 'set clip pan.' This is clear and distinguishes the operation from many set_clip_* siblings, though it largely restates the tool name and does not explicitly differentiate it from alternatives.

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?

There is no guidance on when to use this tool versus alternatives like set_clip_position or set_clip_rotation, nor any mention of preconditions such as a selected clip. The only usage signal is the literal name, so an agent must infer applicability.

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