download_polyhaven_asset

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

No annotations are provided, so the description must fully disclose behavior. It states 'download and import' but does not explain side effects (e.g., scene changes, overwriting, required internet connection, or authentication). This leaves important behavioral traits undisclosed.

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 brief and front-loaded with the main action. It avoids fluff but could be better structured (e.g., bullet points for parameters). Still, every sentence adds value.

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 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain where in Blender the asset is imported, what happens to existing objects, or the return/result. Key context for a download-and-import operation is missing.

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?

With 0% schema description coverage, the description adds meaning for asset_type, resolution, and file_format by listing allowed values. However, the 'asset_id' parameter is not described at all, and the relationship between asset_type and file_format is only partially explained. The description provides some but not comprehensive parameter info.

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 downloads and imports a PolyHaven asset into Blender, specifying acceptable asset types (hdris, textures, models), resolutions (1k, 2k, 4k), and file formats per type. This distinguishes it from siblings like search_polyhaven_assets or download_sketchfab_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?

While the description implies the tool is for PolyHaven assets, it does not explicitly state when to use it over alternatives or when not to use it. With many sibling tools, explicit guidance on preconditions or exclusions (e.g., needing an asset ID from search) would improve clarity.

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