add_transition

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

Lacks annotation coverage entirely. Mentioning 'Uses QE DOM' adds minimal insight. Does not disclose side effects, stability, authorization needs, or whether it modifies the timeline permanently. For a mutation tool with no annotations, this is insufficient.

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?

Extremely concise at two sentences with no wasted words. The purpose and mechanism are front-loaded, though the 'Uses QE DOM' could be omitted.

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?

Lacks any information about return values, success indicators, or error conditions. Since no output schema exists, the description should compensate. Still, for a simple add operation, it provides the minimal necessary context for basic use.

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 adequate descriptions for all parameters. The description adds no extra value beyond listing the parameters; it does not elaborate on defaults, constraints, or relationships between 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?

Clearly states it adds a video transition at a cut point between two clips, differentiating it from 'add_transition_to_clip' and 'batch_add_transitions'. The verb 'Add' and resource 'video transition' are specific.

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 on when to use this tool over siblings like 'add_transition_to_clip' or 'batch_add_transitions'. Does not mention prerequisites such as having the active sequence or a valid timeline.

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