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 mentions 'timeout protection included', 'Performance: Depends on file size and network speed', and 'Security: Validates URLs, enforces timeouts, saves within project directory'. While annotations cover basic safety (destructiveHint=false), the description provides practical implementation details about network dependencies and security measures that help the agent understand runtime behavior.

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-loads the core functionality. While comprehensive, some sections like the detailed examples could be slightly condensed, but overall it's efficient with each section serving a clear 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?

For a file download tool with no output schema, the description provides excellent completeness: it explains what the tool does, when to use it, parameter details, return information ('Download confirmation with file size, type, and save location'), practical examples, performance characteristics, and security considerations. This gives the agent sufficient context to use the 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 repeats parameter information in the Args section but adds minimal extra semantic context beyond what's in the schema. It meets the baseline of 3 by not being misleading, but doesn't significantly enhance parameter understanding beyond the structured 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 specific action ('download file from URL and save to Blender project directory') and resource ('assets, textures, and reference materials'), distinguishing it from sibling tools like blender_save_file for local files. It provides a verb+resource+scope combination that leaves no ambiguity about what the tool does.

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 states 'Use when: Downloading external assets, reference materials, textures from web' and 'Don't use when: Accessing local files (use save_file with local data)', providing clear when-to-use and when-not-to-use guidance with named alternatives. This helps the agent choose between this tool and blender_save_file.

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