set_clip_speed_qe

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

With no annotations, the description carries the full burden. It discloses that the tool uses QE DOM and supports reverse, but does not mention potential side effects, permissions required, limits on speed_percent, or whether the change is reversible. The behavioral information is adequate but incomplete.

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 that includes the core purpose, the method used, and a key feature. No redundant or unnecessary words. It is efficiently front-loaded.

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?

The description covers the basic purpose and a notable feature, but given the tool is a mutation with three parameters and no output schema, it lacks details on return values, error handling, or behavioral constraints. It is minimally adequate for a simple setter.

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?

Schema coverage is 100%, with clear descriptions for all three parameters. The description adds the note 'Supports reverse', which reinforces the reverse parameter but adds minimal new meaning beyond the schema. Baseline 3 is appropriate.

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 it sets clip playback speed using QE DOM, with reverse support. It differentiates from sibling set_* tools by specifying the method and reliability. However, it does not explicitly distinguish from the sibling tool 'speed_change', which might serve a similar 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?

The description mentions it is 'more reliable than ExtendScript', implying a preferred method, but provides no explicit guidance on when to use this tool vs alternatives like 'speed_change' or other speed-related tools. No conditions for when not to use it are given.

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