blender_edit_sequencer

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

Annotations already indicate destructiveHint=true, and the description aligns by mentioning delete operations. It adds context on the range of possible operations (add, modify, delete, effects, transitions), going beyond what annotations provide. No contradiction.

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 sentences, front-loaded with the core purpose, followed by usage guidelines. Every sentence serves a distinct purpose with no wasted words.

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 14 parameters, 100% schema coverage, and no output schema, the description is quite complete. It covers all actions, strip types, and effects. Missing details like return values or error handling, but overall sufficient for a complex editing tool.

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 baseline is 3. The description does not add additional semantics for individual parameters beyond what the schema provides. It groups related operations and types at a high level, but that is more about purpose clarity.

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?

Description clearly states the tool edits the Video Sequence Editor (VSE) with specific actions (add/modify/delete strips, add effects/transitions) and lists supported strip types. It distinguishes from the sibling tool blender_edit_nodes by explicitly excluding compositor node effects.

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 explicit when-to-use and when-not-to-use guidance, including a direct reference to an alternative tool (blender_edit_nodes with tree_type=COMPOSITOR). This helps the agent select the correct tool.

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