set_sequence_pixel_aspect_ratio

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

With no annotations, the description carries full responsibility for disclosing side effects or requirements. It does nothing beyond stating the operation, offering no insight into how it modifies the sequence, whether the sequence must be active, or if the operation is destructive or reversible.

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 under-specified rather than concise. It is a single sentence that merely repeats the tool name and provides no informative content, failing to use the available space to add value.

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 no annotations, no output schema, and zero parameters, the description must explain the tool's effect and prerequisites. It is completely inadequate, consisting only of the tool's name in sentence form, and leaves the agent with no understanding of the operation's context.

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 defines no named parameters and the parameter count is zero. The description adds no clarification about what value is set or how the target sequence is identified, leaving the agent without essential semantics despite the baseline 4 for zero 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 is essentially a restatement of the tool name: 'set sequence pixel aspect ratio.' It adds the prefix 'Premiere Pro expanded operation' but does not explain what pixel aspect ratio affects or distinguish this from the sibling tool 'set_override_pixel_aspect_ratio.' This is a tautology that only clarifies the domain, not the specific behavior.

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 is provided about when to use this tool, prerequisites, or alternatives. It is a bare command with no context for when it should be invoked, and it does not mention any required state such as an active sequence.

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