download_polyhaven_asset

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

No annotations are provided, so the description carries full burden. It states the tool downloads and imports into Blender and returns a success/failure message, but lacks details on import behavior (e.g., overwrite, placement), required Blender context, or error handling. This is insufficient for a mutation tool.

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 structured with a clear opening sentence followed by a bullet-like parameter list. It is front-loaded and every sentence serves a purpose. The parameter explanations, while necessary due to lack of schema descriptions, could be more concise by being moved to the schema.

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 no output schema and no annotations, the description covers the basic operation and parameter meanings. However, it misses prerequisites (e.g., Blender must be running), error handling details, and import specifics. For a tool with 5 parameters and mutation effects, it is adequate but incomplete.

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%, so the description must compensate. It provides brief explanations for each parameter (e.g., 'The ID of the asset to download', examples for resolution and format). However, the descriptions are terse and not exhaustive; for instance, available resolutions are only listed as examples. This adds moderate value over the bare schema.

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 tool's purpose: 'Download and import a Polyhaven asset into Blender.' This is a specific verb+resource combination that distinguishes it from sibling tools like download_sketchfab_model and search_polyhaven_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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or suggest alternative tools for different scenarios. The context of sibling tools (e.g., search_polyhaven_assets) is not leveraged.

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