download_polyhaven_asset

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

With no annotations, the description carries the burden of behavioral disclosure. It states that the tool downloads and imports into Blender and returns a success/failure message, but it does not disclose side effects such as modifying the current scene, network dependency, potential overwrites, or failure modes beyond a generic message.

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 well-structured: a clear purpose sentence, a parameter list, and a return note. The user_prompt paragraph is verbose but carries important behavioral instructions, so the slight extra length is justified.

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?

All parameters are semantically documented and an output schema exists, so the description is largely callable. However, it does not mention how to obtain an asset_id from sibling search tools, nor does it clarify scene-level effects or prerequisites, which matters given the absence of annotations.

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 fully compensates by explaining all five parameters with concrete examples: asset_type lists hdris/textures/models, resolution lists 1k/2k/4k, and file_format gives formats per asset type. The user_prompt parameter gets unusually detailed operational guidance.

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 states a specific verb and resource: 'Download and import a Polyhaven asset into Blender.' This clearly identifies what the tool does and distinguishes it from sibling tools like download_sketchfab_model and download_polypizza_model.

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 main clause implies the tool is for importing Polyhaven assets into Blender, but it gives no explicit when-to-use guidance, exclusions, or alternative tool references. Among many sibling download/search tools, an agent is left to infer routing rather than being directed.

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