set_sequence_pixel_aspect_ratio

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

No annotations are provided, and the description offers no behavioral disclosure. It doesn't state whether this is a mutation, whether it requires a selected sequence, what happens if the sequence is locked, or any side effects. For a setter with zero annotation coverage, this is a significant gap.

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 sentence, efficient and front-loaded with the operation name. It avoids redundancy but could add a bit more useful detail without becoming verbose. The structure is clean.

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?

Given the tool is a mutation (setter) with no annotations, no output schema, and 0 parameters, the description must explain what action it performs and any preconditions. It fails to mention prerequisites like an open project or selected sequence, and it doesn't state what happens if no sequence exists. The completeness is severely lacking.

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 tool has 0 parameters, as correctly reflected in the schema. The description doesn't need to explain parameters, so it doesn't mislead. However, it doesn't explain what input the operation expects (e.g., does it use the current selected sequence and a ratio value?), but with no params, this is acceptable.

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' plus the target resource 'sequence pixel aspect ratio' with 'Premiere Pro expanded operation' context, which distinguishes it from sibling tools like set_sequence_frame_rate. However, it lacks detail on what values can be set or the effect of the operation, making it only slightly above baseline.

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 like set_sequence_settings or set_override_pixel_aspect_ratio. It simply says 'expanded operation' without explaining what that means or when it should be invoked, leaving the agent without clear context.

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