ClaudeKit Blender MCP

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

Annotations already provide idempotentHint=true and destructiveHint=false, but the description adds valuable context: 'Performance: Instant operation, negligible performance impact' and 'Security: Only creates directories within project boundary.' These disclosures about speed and security boundaries go beyond what annotations provide, though it doesn't mention error conditions or permissions.

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 well-structured with clear sections (purpose, args, returns, examples, usage guidance, performance, security). Every sentence adds value without redundancy, and key information is front-loaded in the first sentence.

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?

For a directory creation tool with good annotations (idempotent, non-destructive) and no output schema, the description provides comprehensive context: purpose, parameters, examples, usage guidelines, performance, and security. It doesn't explain return values in detail, but given the annotations and straightforward operation, this is reasonably complete.

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 the schema already documents both parameters fully. The description provides examples showing how directory_path is used (e.g., 'assets/models'), which adds some practical context, but doesn't explain parameter interactions or edge cases beyond what's in the schema.

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 creates a new directory within the Blender project structure, specifying the exact resource (directory) and action (create). It distinguishes from sibling tools like 'blender_save_file' by focusing on directory creation rather than file 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 provides 'Use when' scenarios (setting up project structure, organizing assets, creating workflow folders) and 'Don't use when' guidance (creating files, with alternative 'save_file' named). This gives clear context for when to select this tool versus alternatives.

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