ClaudeKit Blender MCP

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

The description adds valuable behavioral context beyond annotations: it discloses performance characteristics ('typically fast for assets under 100MB') and security constraints ('Validates file paths and saves within project directory'). While annotations already indicate destructiveHint=true, the description provides practical implementation details that help the agent understand operational boundaries.

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 guidelines, performance, security) and front-loaded with the core functionality. While comprehensive, some sections like the detailed examples could be slightly condensed, but overall it's efficiently organized with minimal redundancy.

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 (file operations with security implications) and the absence of an output schema, the description provides excellent completeness. It covers purpose, parameters, return values, examples, usage scenarios, performance expectations, and security constraints - everything needed for an agent to use this tool effectively despite the lack of structured output documentation.

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 100% schema description coverage, the schema already documents all three parameters thoroughly. The description's 'Args' section essentially repeats what's in the schema without adding significant additional semantic context. The examples provide some usage context but don't enhance parameter understanding beyond the schema's 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 the specific action ('Save base64 encoded file data') and resource ('to the Blender project directory'), with examples distinguishing it from sibling tools like blender_export_asset or blender_download_file. It explicitly mentions supporting various file types including assets, textures, and project files.

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 explicit 'Use when' and 'Don't use when' sections with clear alternatives named ('use Blender export tools'). It gives concrete scenarios like 'Saving downloaded assets, exporting files, project file management' and warns against using it for 'Creating files from Blender operations'.

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