BlenderMCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the action ('Download and import') and return value ('message indicating success or failure'), it lacks critical details: whether this requires internet connectivity, what happens if assets already exist, file storage locations, Blender integration specifics, error conditions, or performance characteristics. The description covers basic operation but misses important behavioral context for a download/import tool.

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 efficiently structured with a clear purpose statement followed by a bulleted parameter explanation and return value note. Every sentence earns its place by adding value, with no redundant or verbose content. The information is front-loaded and well-organized for quick comprehension.

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 (download + import operations), lack of annotations, and absence of output schema, the description provides adequate basic information but has significant gaps. It covers the what and how of parameters well, but misses important contextual details about the Blender integration process, file handling, error scenarios, and operational constraints that would be needed for reliable 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?

The description provides meaningful semantic context for all 4 parameters beyond the schema's 0% coverage. It explains what each parameter represents (asset ID, type, resolution, format) and gives concrete examples of valid values for asset_type, resolution, and file_format. This significantly compensates for the schema's lack of descriptions, though it doesn't specify value constraints or dependencies between parameters.

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 ('Download and import'), target resource ('Polyhaven asset'), and destination ('into Blender'), distinguishing it from sibling tools like 'search_polyhaven_assets' or 'import_generated_asset'. It explicitly combines download and import operations in one 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 implies usage when needing to obtain Polyhaven assets for Blender, but provides no explicit guidance on when to use this tool versus alternatives like 'import_generated_asset' or 'download_sketchfab_model'. It doesn't mention prerequisites, constraints, or comparative scenarios with sibling tools.

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