Reverse Clip

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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds useful context that the operation is unsupported by Premiere's scripting API, but it does not state what actually happens if the tool is called, such as whether it errors, no-ops, or returns an error payload.

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, front-loaded sentence that begins with the most important information: "Unavailable." Every part of the sentence earns its place, and there is no filler.

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 that an output schema exists and annotations cover the safety profile, the description need not explain return values. It adequately communicates the tool's unavailability, but it omits what an agent should do instead and what invocation failure behavior to expect.

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 description coverage is 100%, so node_id and reverse are fully documented in the schema. The description adds no parameter-level meaning beyond that, which makes the baseline score of 3 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 states the specific intended action, reversing a timeline clip's playback direction, and immediately qualifies it as unavailable because Premiere lacks a supported scripting API. This is clear and distinguishable from siblings, though it does not point to any alternative tool or workflow.

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 word "Unavailable" gives the agent a strong signal not to invoke this tool for reversal. However, it does not name an alternative such as speed_change or set_clip_speed_qe, so the agent is left without a routing option when reverse capability is needed.

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