BlenderMCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'downloads and imports' and 'returns a message indicating success or failure', but fails to cover critical aspects like whether this is a read-only or destructive operation, potential rate limits, authentication needs, or how errors are handled. This leaves significant gaps for a tool that interacts with external assets.

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 appropriately sized and front-loaded, starting with a clear purpose statement followed by a structured parameter list. Every sentence adds value, with no wasted words, though the return statement could be slightly more informative.

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 complexity of downloading and importing external assets, no annotations, and no output schema, the description is moderately complete. It covers the basic purpose and parameters but lacks details on behavioral traits, error handling, and integration with Blender, which are crucial for safe and effective use.

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 effectively adds meaning by explaining each parameter's purpose, providing examples for 'resolution' and 'file_format', and noting that 'file_format' is optional. This clarifies semantics beyond the bare schema, though it could benefit from more detail on allowed values or constraints.

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 ('download and import') and resources ('Polyhaven asset into Blender'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'import_generated_asset' or 'download_sketchfab_model', which handle similar operations for different sources.

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 no guidance on when to use this tool versus alternatives like 'import_generated_asset' or 'download_sketchfab_model'. It also lacks information about prerequisites, such as whether Blender needs to be running or if specific permissions are required, leaving the agent with no context for tool selection.

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