blender_vse

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

No annotations are provided, so the description carries the full burden. It comprehensively lists all 20 operations and their effects, such as adding strips, trimming, muting, and rendering. However, it does not disclose side effects (e.g., whether operations modify current Blender state or are undoable). Given the extensive operation listing, it is fairly transparent.

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 structured with clear categories and operation lists, which aids readability. However, the first paragraph about 'PORTMANTEAU PATTERN RATIONALE' is somewhat verbose for an AI agent and could be condensed. Overall, it is well-organized and front-loaded with purpose.

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 tool's complexity (40 parameters, 20 operations), the description is comprehensive. It covers all operation categories and indicates which parameters are needed for each. The output schema exists but is not detailed here; still, the description provides sufficient context for use. Minor gaps exist, such as missing error handling or state constraints.

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?

The schema has 78% description coverage, so the baseline is 3. The description adds value by mapping operations to required parameters (e.g., 'Required for: add_movie, add_sound' for filepath). It also groups operations, enhancing understanding of which parameters are relevant for each task. This goes beyond the schema's individual property descriptions.

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 clearly states that the tool consolidates 20 VSE operations into a single interface for video editing. It lists all operations in categories (strip creation, editing, properties, etc.) and explicitly mentions capabilities like strip management, timeline editing, effects, and rendering. This distinguishes it from sibling tools that focus on other Blender domains.

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 description provides a rationale for the portmanteau pattern but does not explicitly guide when to use this tool versus alternatives. There is no mention of prerequisites, when not to use, or how to choose among the 20 operations. The categorized list of operations gives some implicit guidance, but no clear usage rules are stated.

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