Add transition (QE)

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

Annotations already declare destructiveHint=true, indicating mutation. Description adds that clipIndex is 0-based and mentions experimental nature, which is useful. However, it does not disclose potential failure modes or side effects beyond the annotation.

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?

Three focused sentences with no wasted words. Front-loaded with the tool's purpose, then important caveats and parameter details.

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?

Covers all parameters with defaults, experimental status, and indexing detail. Lacks mention of return value or failure handling, but since there is no output schema, the description is reasonably complete for a 5-parameter tool with no required params.

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%, but description adds default values for each parameter (e.g., name='Cross Dissolve', duration=0.5) and clarifies clipIndex is 0-based. This adds meaning beyond the schema's min constraints.

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?

Clearly states it adds a video transition to a clip's cut, with examples like 'Cross Dissolve'. The verb 'add' and resource 'transition' are unambiguous, and it distinguishes from sibling tools like 'premiere_add_effect' by specifying it's for transitions.

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?

Provides context by noting it's experimental and unsupported but works on PPro 25, guiding agents to use cautiously. Does not explicitly state when not to use or list alternatives, but the context is sufficient for typical use.

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