download_polyhaven_asset

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It signals a state-changing operation by saying 'download and import,' but it does not explain side effects, required network access, how the import interacts with the current Blender scene, or whether the operation blocks.

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 a single sentence with no filler, front-loading the core action and target. It is concise and clear, though it lacks supporting context that would make it more informative.

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?

With no output schema and no annotations, the description should explain expected outcomes, errors, and behavioral effects. It does not mention return values, where the asset is saved, what happens on failure, or how long the operation might take, leaving significant gaps for a mutating tool.

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?

The input schema provides a description for all four properties, including allowed values for asset_type, resolution, and file_format. The description adds no parameter-level detail, but at 100% schema description coverage, the baseline of 3 applies.

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 uses specific verbs ('download' and 'import'), a clear resource ('PolyHaven asset'), and a clear destination ('Blender'). It also distinguishes itself from siblings that operate on Sketchfab, Hyper3D, or Hunyuan3D assets.

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?

No guidance is given on when to use this tool versus alternatives like search_polyhaven_assets, import_generated_asset, or download_sketchfab_model. There is no mention of prerequisites, such as needing to search for the asset first or knowing its ID.

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