download_polyhaven_asset

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

With no annotations, the description must disclose all behavioral traits. It only states it downloads and imports, returning success or failure. Missing details: whether it overwrites existing assets, requires internet access, handles errors (e.g., invalid asset_id), or any side effects on the Blender scene.

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 relatively concise, with a clear verb-action and a parameter list. It avoids unnecessary words. However, the parameter list is somewhat redundant given the input schema, though it adds value due to zero schema coverage. Slightly better structuring (e.g., using bullet points) could improve readability.

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 covers the basic purpose and parameter meanings. Missing elements: usage prerequisites (e.g., Blender scene must be open?), error scenarios, and behavior when resolution or format is unsupported. Adequate but has clear gaps.

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%, so the description is the sole source for parameter meaning. It explains each parameter and provides examples (e.g., 'hdris, textures, models' for asset_type). However, it lacks explicit valid values or format constraints, and does not clarify default behavior (e.g., resolution default '1k' is in schema but not described).

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 that the tool downloads and imports a Polyhaven asset into Blender. It lists asset_id, asset_type, resolution, and file_format, making the function obvious. It is distinct from sibling tools like search_polyhaven_assets and get_polyhaven_status.

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 provides no guidance on when to use this tool versus alternatives like search_polyhaven_assets (for discovery) or import_generated_asset (for importing custom assets). There is no mention of when not to use it, such as when the asset is already present or if offline.

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