set_sequence_pixel_aspect_ratio

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 explaining side effects. It only says 'set sequence pixel aspect ratio' without disclosing whether this mutates the active sequence, whether it is undoable, what value format is expected, or what result is returned. The mutating nature is implied but not elaborated.

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 brevity here reflects under-specification rather than conciseness. The phrase 'Premier Pro expanded operation' is generic filler and repeats the tool's name without adding usable information. Important operational details are absent.

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 mutating tool with no annotations, no output schema, and no parameter definitions, the description is far too thin. It does not explain how to provide the pixel aspect ratio, which sequence is affected, when to prefer this over similar tools, or what happens after execution. An agent has almost no reliable basis for invoking this tool correctly.

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?

Although the schema reports zero parameters, the operation is a 'set' action and logically requires an aspect ratio value. The schema uses `additionalProperties: true`, so arbitrary inputs are accepted, but the description does not specify the expected parameter name, value format, or examples. The empty schema and vague description leave the agent unable to construct a correct call.

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 verb and resource: 'set sequence pixel aspect ratio.' This identifies the operation and distinguishes it from clip-level pixel aspect ratio operations like set_override_pixel_aspect_ratio, though it does not explicitly call out that sibling. The 'Premiere Pro expanded operation' prefix is filler but does not obscure the core 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?

There is no guidance on when to use this tool versus related tools such as set_override_pixel_aspect_ratio, set_sequence_settings, or set_sequence_resolution. No prerequisites or context (e.g., whether an active sequence must be selected) are mentioned, 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.