add_transition

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not mention whether the operation is destructive, if it modifies the timeline in place, or any permission or format requirements. For a mutation tool that likely alters the timeline, this lack of transparency is a significant gap.

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 with no fluff, so it is concise. However, conciseness must be balanced with informativeness. Here, it is too brief and slightly misleading, which reduces effectiveness. It is average in 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 complexity of 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what happens when a transition is added, how it affects the timeline, or any constraints (e.g., overlapping transitions). An agent would lack key context to use the tool correctly.

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 only 17% (only clip_id has a description). The tool description adds no additional meaning to the parameters; it does not explain the role of filepath, output_path, duration, or the specific transition types. Since schema coverage is low, the description should compensate but fails to do so.

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 'Add a transition between clips' is somewhat clear but misleading. In video editing, a transition typically occurs between two clips, but the schema suggests it is applied to a single clip (with positions start/end/both). This ambiguity could confuse an AI agent. It does state the verb and resource, but the wording is imprecise.

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 like split_clip or apply_template. There is no mention of prerequisites, context, or scenarios where this tool is appropriate versus others. The description fails to help the agent select this tool over siblings.

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