set_clip_anchor_point

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

Despite annotations providing no behavioral hints (destructiveHint false, readOnlyHint false), the description does not elaborate on side effects, requirements (e.g., does clip need a Motion effect?), or whether it modifies existing anchor point or sets for the first time. Minimal behavioral transparency.

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?

Single sentence, no fluff, directly states the tool's purpose. Perfectly concise for a simple setter.

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?

No output schema, and the description lacks context about the effect on other clip properties (e.g., scaling, rotation), default anchor point behavior, or whether the Motion effect must already exist. For a mutation tool with 3 params, more contextual details would aid correct invocation.

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?

Schema coverage is 100% with parameter descriptions in the schema (coordinates in pixels, node ID). The tool description adds no further semantics beyond restating 'Anchor Point property'. Baseline 3 is appropriate as the schema already documents parameters adequately.

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 it sets the Anchor Point property on a video clip's Motion effect, distinguishing it from other clip property setters like set_clip_position or set_clip_scale. However, it could be more precise about what anchor point means (pivot point for transformations).

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 vs alternatives (e.g., set_clip_position). No context about prerequisites or typical use cases. The description only states what it does, not when to apply it.

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