set_override_pixel_aspect_ratio

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

With no annotations, the description must carry the full behavioral burden. It only indicates a mutation (setting), but does not disclose whether it modifies a clip, sequence, or project setting, whether it is reversible, or what side effects occur. Minimal warning about its impact is given.

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 with no fluff, but it is under-specified. It lacks even a basic subject (e.g., what is being overridden) and would benefit from a brief example or qualifier. Minimal structure does not add clarity.

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, no output schema, and no parameters, the description is entirely inadequate. It does not explain what 'override' means, what values are valid, or what the effect is. An agent cannot correctly invoke this tool based solely on the given text.

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 has no defined parameters (allows any properties), and the description does not mention a required value such as a ratio number. The baseline for 0 params is 4, but the tool clearly needs an argument to set a value, and the description offers no hint about how to specify it, so it fails to compensate.

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 states a clear action ('set') and a specific resource ('override pixel aspect ratio'), which conveys the basic purpose. However, it does not distinguish this tool from similar siblings like set_sequence_pixel_aspect_ratio or set_footage_interpretation, leaving ambiguity about the exact scope (e.g., clip vs. sequence).

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. No context about prerequisites, typical scenarios, or why an agent would choose this over related aspect-ratio tools is provided, leaving the agent to guess.

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