download_polyhaven_asset

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

No annotations exist, so the description carries full burden. It discloses the action (download and import) and return type (success/failure message), but omits critical behavioral details such as whether importing overwrites existing data, file path conventions, authorization needs, or error handling.

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 with a one-line summary then structured parameter list. It is front-loaded with the core purpose. The return message description is minimal but adequate.

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 and import with multiple formats), the description covers purpose, parameters, and return type but lacks behavioral context (e.g., side effects, prerequisites). Absence of output schema increases the need for such detail.

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%, but the description explains each parameter's purpose and provides type-specific examples for asset_type and file_format. This adds meaningful guidance beyond the bare schema, though enumeration of valid values is incomplete.

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 verb 'download and import' and the resource 'Polyhaven asset into Blender'. It is distinct from sibling tools like search_polyhaven_assets or get_polyhaven_categories, which serve different purposes.

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 the tool is for downloading assets but does not explicitly state when to use it versus alternatives (e.g., after searching with search_polyhaven_assets). No exclusions or when-not-to-use guidance is provided.

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