set_clip_pan

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention that the operation modifies a clip property, any side effects, permissions, or state requirements. It gives no indication of the operation's nature beyond the word 'set,' which is insufficient.

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 but under-specified. It starts with a generic prefix ('Premiere Pro expanded operation') that adds no value, followed by a restatement of the tool name. It lacks the structural content needed to be useful, making it barely more than a placeholder.

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 the absence of annotations, output schema, and explicit parameters, the description needs to provide comprehensive usage context. It fails to explain what 'pan' means, what the operation does, what inputs are required, or how it fits with existing clip property setters, making it severely incomplete.

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 input schema is permissive (allows any properties) and defines no explicit parameters, while the context signal reports 0 parameters. The description does not mention the needed 'pan' value, its type, range, or unit. Thus, an agent cannot infer what arguments to pass when invoking this tool.

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 is 'Premiere Pro expanded operation: set clip pan.' This essentially restates the tool name without clarifying what 'pan' refers to (audio pan, spatial pan, etc.). It does not distinguish from sibling tools like set_clip_position or set_clip_volume, so it fails to clearly define the tool's unique purpose.

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 omits context such as prerequisites (e.g., selected clip), alternatives, or scenarios where this operation is appropriate, leaving the agent without any basis for tool selection.

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