download_polyhaven_asset

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

No annotations provided, so the description carries full burden. It only mentions returns (success/failure) and omits behavioral traits like destructive effects (import modifies scene), network dependency, or any side effects. This is insufficient for a tool that downloads and imports assets.

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?

Description is concise with about 10 lines, listing parameters clearly. No redundant sentences. Could be structured more formally but remains 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 moderate complexity (4 params, no output schema), the description covers parameter purposes but lacks details on import behavior (e.g., overwriting, scene placement, error handling). Not fully comprehensive but adequate for basic usage.

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 coverage is 0%, but the description adds meaning by explaining each parameter (asset_id, asset_type, resolution, file_format) and providing format examples based on asset type. This compensates for the lack of schema descriptions.

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 action ('Download and import a Polyhaven asset into Blender') and the resource (Polyhaven asset). It distinguishes itself from sibling tools like 'download_sketchfab_model' and 'search_polyhaven_assets' by specifying the source and action.

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 for downloading Polyhaven assets but does not explicitly state when to use vs. alternatives (e.g., after searching, or when not to use). It lacks exclusions or context about prerequisites.

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