polyhaven_download

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the main side effects: downloading and importing assets as world lights, PBR materials, or scene models. However, it omits network dependency, download location, potential overwrites, and failure modes, which are relevant for a download/import operation.

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 compact and front-loaded, using an efficient arrow notation to convey the type-specific behavior. The resolution fragment is minimal but useful. It could be slightly more structured, but there is no wasted text.

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?

For a tool with four parameters, no annotations, and no output schema, the description is incomplete. It fails to document required parameter formats, valid asset_type values, and file_format options, leaving an agent to guess critical invocation details.

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%, and no enums exist, so the description must compensate for all parameter documentation. It only mentions resolution values and implies asset_type categories; asset_id and file_format are left completely undefined. This is insufficient for correct invocation.

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-resource pair ('下载 Poly Haven 资产并导入') and clearly distinguishes the tool from siblings like polyhaven_search and sketchfab_download. The asset-type mapping (HDRI→world light, texture→PBR material, model→scene) makes the purpose unmistakable.

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 gives clear context for when to use this tool: to download Poly Haven assets and import them into Blender with type-appropriate handling. It does not explicitly name alternatives or exclusions, but the source and behavior are specific enough that an agent can infer the intended usage.

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