blender_vse

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

Annotations are all false, so the description carries the full burden. It lists operations like clear_vse and delete_strip but does not disclose that these are destructive or that all operations mutate the current Blender session. There is no mention of side effects, permissions, or whether changes are reversible. The 'Follows FastMCP 3.x best practices' note adds no behavioral insight.

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 long (around 500 words) and includes a 'PORTMANTEAU PATTERN RATIONALE' that is partially redundant with the first paragraph. However, the categorized operation list is necessary for a 20-operation tool. The structure is clear, but some sentences could be trimmed without losing value.

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 (40 parameters, 20 operations), the description provides a comprehensive op list and categories. However, it does not explain how the 'operation' parameter dispatches sub-operations, what the default operation is (list_strips), or the execution context (e.g., requires running Blender). It also omits behavioral details about state persistence and error conditions. Adequate but with gaps.

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?

With 78% schema coverage, the baseline is 3. The description adds operation-to-parameter mappings (e.g., 'add_movie' requires 'filepath', 'add_effect' uses 'strip1_name' and 'strip2_name'), which is critical for a portmanteau tool with 40 parameters. This helps the agent select the right parameters per operation beyond what the schema alone provides.

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 the tool exposes Blender's Video Sequence Editor as MCP tools, with a specific verb ('add', 'apply', 'trim', 'cut', 'move', 'render') and resource (VSE). It distinguishes itself from sibling tools like blender_compositor and blender_render by focusing on VSE operations.

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 explicitly says it consolidates 20 VSE operations to prevent tool explosion, which implies when to use this tool (for video editing tasks). It provides categorized operation lists that guide sub-operation selection. However, it does not explicitly mention when NOT to use it or name alternative tools.

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