BlenderMCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions executing code 'in Blender' and advises step-by-step chunking, but lacks critical details: it doesn't specify execution context (e.g., in Blender's Python environment), safety considerations (e.g., potential for destructive operations), permissions needed, rate limits, or error handling. This is inadequate for a tool that runs arbitrary code.

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 concise and front-loaded: the first sentence states the purpose, followed by usage advice and parameter details. It avoids redundancy, but the parameter section could be integrated more smoothly. Overall, it's efficient with minimal waste.

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 complexity (executing arbitrary code), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It misses critical context: execution environment details, safety warnings, return values, or error behavior. This leaves significant gaps for an AI agent to use the tool effectively.

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 0%, so the description must compensate. It lists the parameter 'code' and explains it as 'The Python code to execute,' adding basic meaning beyond the schema's title 'Code.' However, it doesn't provide details on code format, constraints, or examples. With only one parameter, this is minimally adequate but leaves gaps.

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: 'Execute arbitrary Python code in Blender.' It specifies the verb ('Execute') and resource ('Python code in Blender'), making it distinct from sibling tools that handle downloads, searches, imports, or status checks. However, it doesn't explicitly differentiate from potential code-related siblings, though none are listed.

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 some usage guidance: 'Make sure to do it step-by-step by breaking it into smaller chunks.' This implies a best practice for using the tool but doesn't specify when to use it versus alternatives (e.g., for automation vs. other Blender operations) or any prerequisites. No explicit alternatives or exclusions are mentioned.

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