ClaudeKit Blender MCP

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

The description adds valuable behavioral context beyond annotations: 'Permanently removes object and its data. Cannot be undone via MCP.' and 'Error: "Object not found" if object doesn't exist'. While annotations already indicate destructiveHint=true and idempotentHint=true, the description clarifies the permanence and error behavior, enhancing transparency.

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, Use when, Don't use when, Error) and avoids redundancy. It's appropriately sized, though the Args and Returns sections could be slightly more concise given the simple parameter and return.

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 destructive tool with one parameter and no output schema, the description is complete: it explains the action, usage guidelines, behavioral traits (permanence, error handling), and parameter semantics. It compensates well for the lack of output schema by mentioning return confirmation.

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 the single parameter 'object_name' as 'Object to delete'. The description repeats this in the Args section but doesn't add significant semantic context beyond what's in the schema, such as naming conventions or constraints, meeting the baseline for high schema coverage.

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 ('Delete object from Blender scene by name') and distinguishes it from sibling tools like 'blender_modify_object' or 'blender_get_object_info'. It specifies both the verb (delete) and resource (object) with precision.

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 provides 'Use when: Cleaning up scene, removing unwanted objects' and 'Don't use when: Temporarily hiding objects (no hide functionality in MCP currently)', offering clear guidance on when to use this tool versus alternatives. It even explains why not to use it for hiding.

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