BlenderMCP

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

No annotations are provided, so the description carries full burden. It mentions returns a list with basic information but lacks details on pagination, rate limits, authentication needs, or error handling. For a search tool with no annotation coverage, this is a significant gap in behavioral disclosure.

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 with three sentences: purpose, parameters, and returns. It's front-loaded with the main function. Some minor redundancy exists (e.g., 'optional filtering' could be inferred from parameters), but overall efficient.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It covers basic purpose and parameters but lacks details on return structure, error cases, or integration with siblings like download_polyhaven_asset. For a search tool in this context, more guidance is needed.

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 explains asset_type options (hdris, textures, models, all) and categories as comma-separated list, adding meaning beyond the schema's generic titles. However, it doesn't clarify format for categories or default behaviors, leaving some 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 searches for assets on Polyhaven with filtering, which is a specific verb (search) and resource (assets). It distinguishes from siblings like download_polyhaven_asset (which retrieves) and search_sketchfab_models (which searches a different platform). However, it doesn't explicitly contrast with get_polyhaven_categories, which might provide related metadata.

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. It mentions optional filtering but doesn't specify scenarios for using search_polyhaven_assets over get_polyhaven_categories for category info or download_polyhaven_asset for retrieval. No exclusions or prerequisites are stated.

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