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 collections can be nested hierarchically, mentions performance characteristics ('Instant operation, negligible performance impact'), and provides practical examples. While annotations cover idempotency and safety, the description enriches understanding with real-world usage patterns.

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?

Well-structured with clear sections (purpose, explanation, Args, Returns, Examples, usage guidelines, performance). While slightly longer than minimal, each section adds value. The front-loaded purpose statement is clear, and subsequent information is organized logically without 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 moderate complexity (2 parameters, no output schema), the description provides comprehensive context: purpose, usage guidelines, parameter examples, return information, and performance characteristics. It compensates well for the lack of output schema by describing what to expect ('Collection creation confirmation and collection information').

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 both parameters thoroughly. The description's Args section repeats schema information without adding significant semantic context. The examples provide some usage context but don't enhance parameter understanding beyond what's in 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 tool creates a new Blender collection for organizing assets, specifying both the verb ('create') and resource ('Blender collection'). It distinguishes from siblings like blender_add_to_collection (adds existing objects) and blender_list_collections (reads collections).

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?

Explicit 'Use when' and 'Don't use when' sections provide clear guidance on when to select this tool versus alternatives. It specifies appropriate contexts (organizing scene assets, creating libraries) and when to avoid (single objects without organization needs), helping the agent make correct decisions.

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