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 explains that 'Objects in Blender can belong to multiple collections' (important context), mentions 'flexible asset organization and scene management' (use case), and provides performance information ('Instant operation, negligible performance impact'). While annotations cover safety (non-destructive, idempotent), the description enriches understanding of the tool's behavior in the Blender context.

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) and every sentence adds value. It's front-loaded with the core functionality, followed by supporting details, with no redundant or wasted text.

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 tool with 3 parameters, good annotation coverage (idempotent, non-destructive), and no output schema, the description provides comprehensive context: clear purpose, parameter guidance, usage boundaries, performance characteristics, and practical examples. It addresses what the tool does, when to use it, and what to expect, making it complete for agent decision-making.

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 67% schema description coverage (2 of 3 parameters have descriptions), the description adds meaningful context: it explains the boolean parameter's effect ('Remove from other collections') and provides concrete examples showing how parameters interact in different scenarios. The examples illustrate the practical implications of parameter choices beyond what the schema 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 specific action ('Move or copy an object to a specific collection') and resource ('object', 'collection'), distinguishing it from sibling tools like 'blender_create_collection' (creation) and 'blender_delete_object' (deletion). The opening sentence provides immediate clarity about the tool's function.

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 includes explicit 'Use when' and 'Don't use when' sections with concrete examples ('Organizing scene assets', 'Creating new objects'), plus named alternatives ('use object creation tools instead'). This provides clear guidance on when to select this tool versus other options.

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