set_clip_anchor_point

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 disclosing behavior. It merely restates that the tool sets an anchor point and says nothing about mutation, selection requirements, coordinate semantics, reversibility, or side effects. This adds essentially no behavioral information beyond the tool's name.

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 it is essentially a restatement of the tool name plus the unhelpful filler 'expanded operation.' This is under-specification rather than disciplined conciseness; the only sentence does not earn its place with new information.

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 tool with no annotations and no output schema, the description omits crucial context such as whether a clip must be selected, what anchor point coordinates mean, and how this relates to scaling or rotation. An agent cannot reliably infer the expected behavior or preconditions from this description.

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 has zero documented parameters, so the description has little to compensate for. The baseline of 4 applies because there are no parameter semantics to explain, and the description does not need to fill a schema coverage gap.

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 identifies the action (set) and the resource (clip anchor point), which is enough to distinguish it from siblings like set_clip_position or set_clip_rotation. However, the 'Premiere Pro expanded operation' prefix is vague and largely restates the tool's name without adding meaningful clarification.

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 any of the many set_clip_* alternatives, nor any mention of prerequisites such as a selected clip. The description gives no context for choosing between this and related clip-transformation tools.

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