ClaudeKit Blender MCP

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds valuable behavioral context beyond annotations: performance characteristics ('Fast operation, minor impact with large recursive listings') and security boundaries ('Only accesses files within project directory structure'). No contradiction with annotations.

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). While comprehensive, some sections like the performance and security notes could be more concise. The front-loaded purpose statement is clear, but the overall length is slightly longer than necessary.

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 read-only listing tool with comprehensive annotations and 100% schema coverage, the description provides good contextual completeness. It covers purpose, usage guidelines, examples, performance, and security considerations. The main gap is the lack of output schema, but the description's 'Returns' section provides reasonable metadata information about what to expect.

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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description's 'Args' section repeats what's in the schema without adding significant semantic context beyond what's already captured in structured fields. The examples provide some usage context but don't fundamentally enhance parameter understanding beyond the 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 verb 'List' and resource 'files and directories in the Blender project or specified directory'. It distinguishes itself from siblings like create_directory and save_file by being a read-only listing operation rather than a creation/modification tool.

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' scenarios (project organization, asset management, file system navigation) and 'Don't use when' alternatives (creating new files or directories, directing to create_directory/save_file). This gives clear guidance on when to select this tool versus other available options.

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