set_sequence_resolution

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

With no annotations provided, the description must fully disclose behavior. It does not mention that this is a mutating operation, whether it requires an active sequence, what happens to existing settings, or how resolution is specified. The description is too vague to inform the agent about side effects or constraints.

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 extremely short, but it is under-specified rather than appropriately concise. It essentially restates the tool name and adds the vague 'expanded operation' phrase. The single sentence does not earn its place because it contributes no additional clarity or structure.

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 mutation nature and lack of output schema or annotations, the description is incomplete. It does not explain the effect of the operation, how the resolution is determined, or any side effects. The agent would have to guess about the tool's behavior and relationship to other sequence-setting tools.

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 input schema has zero parameters and 100% coverage, so the baseline is 4. The description does not add parameter information, but none is needed since the tool takes no formal parameters. It maintains the baseline without adding confusion.

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 action: 'set sequence resolution'. It uses a specific verb+resource pattern, though it doesn't differentiate from sibling tools like set_sequence_settings or set_sequence_pixel_aspect_ratio. The phrase 'Premiere Pro expanded operation' adds no meaningful distinction.

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 on when to use this tool versus alternatives. The description lacks any context about prerequisites, active sequence requirements, or interaction with other sequence settings. It merely states what it does without indicating appropriate usage scenarios.

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