ClaudeKit Blender MCP

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

The description adds valuable behavioral context beyond what annotations provide. Annotations indicate read-only, non-destructive, and idempotent operations, but the description adds 'Performance: Instant operation, negligible performance impact' which gives practical implementation insight. It doesn't contradict annotations and provides additional useful information about execution characteristics.

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 (description, Args, Returns, Examples, Use when, Don't use when, Performance) and every sentence earns its place. It's appropriately sized for the tool's complexity, front-loading the core purpose while providing necessary details in organized subsections 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 simple nature (single parameter with full schema coverage, read-only operation with comprehensive annotations), the description provides complete contextual information. It covers purpose, usage guidelines, parameter examples, behavioral characteristics, and distinguishes from related tools, making it fully adequate for agent understanding despite the lack of output schema.

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 for the single parameter, the schema already documents the 'operation' parameter with its enum values and default. The description adds minimal value beyond the schema by mentioning the parameter in the Args section and providing examples, but doesn't add significant semantic context beyond what's already 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's purpose with specific verbs ('List all supported file formats') and resources ('import and export operations'), distinguishing it from sibling tools like import_asset and export_asset. It goes beyond just restating the name/title by specifying what information is provided ('comprehensive format information with capabilities and recommended use cases').

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 guidance on when to use ('Use when: Planning asset workflows, choosing formats, understanding capabilities') and when not to use ('Don't use when: Actual import/export operations (use import_asset/export_asset instead)'), including named alternatives. This gives clear context for tool selection versus its siblings.

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