set_anti_alias_quality

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It implies a mutation (setting a property) but does not mention side effects, prerequisites (e.g., clip must have a Motion effect), or what happens when anti-aliasing is disabled. The description is adequate but lacks depth.

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 a single, concise sentence (15 words) that front-loads the purpose and context. No unnecessary words or redundancy.

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 tool with two boolean/string params and no output schema, the description is fairly complete. It explains the purpose and usage context. However, it omits potential error conditions (e.g., clip without Motion effect) and any return value, but these gaps are minor given the tool's simplicity.

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 clear param descriptions. The tool description adds meaningful context beyond the schema, explaining that the operation targets the Motion effect and is relevant for scaled/rotated clips. This helps an agent understand when to adjust these parameters.

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 the verb 'Set', the resource 'anti-alias quality on a clip's Motion effect', and provides context ('useful for scaled/rotated clips'). It distinguishes itself from sibling set_* tools by being specific to anti-aliasing.

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 includes usage context ('useful for scaled/rotated clips') indicating when to consider this tool. It does not explicitly say when not to use it or list alternatives, but the context is clear enough for an AI agent to decide.

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