blender_polyhaven_download

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

With no annotations, the description carries the full disclosure burden. 'Download and apply' implies a network operation that mutates the Blender scene, but it does not mention licensing, download time/size, object/material selection side effects, undo behavior, or failure modes.

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 very short and front-loaded, which is good for scanability. However, it is sparse enough that it mostly restates the tool name plus 'apply' and does not enrich the agent's understanding much beyond the name itself.

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 the absence of annotations and an output schema, this description is too thin for a tool that downloads and applies external assets. It omits the workflow connection to blender_polyhaven_search, asset-type behavior, and practical expectations like network access or scene impact.

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 100%, so the baseline is 3; the schema already documents asset_id, apply_to, and resolution. The description adds no extra parameter-level meaning, such as which asset types require apply_to or how resolution interacts with asset type.

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 action ('Download and apply') on a specific resource ('Poly Haven asset'), so an agent can tell this tool is about acquiring and using assets. It does not explicitly distinguish itself from sibling blender_polyhaven_search, though the verb 'apply' implies more than searching.

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?

There is no guidance on when to use this tool versus alternatives, such as using blender_polyhaven_search first to find an asset ID. It also does not clarify when apply_to is needed, which asset types are supported, or what happens for non-texture assets.

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