download_polyhaven_asset

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

With no annotations, the description fails to disclose important behavioral traits such as whether the asset overwrites existing files, requires an internet connection, or has any side effects in Blender. Only the basic action and return message are mentioned.

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 extremely concise: two sentences plus a parameter list. It is front-loaded with the core purpose and uses a clear bullet format for parameters. No extraneous information.

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?

The description covers the parameters and basic return, but lacks context about the import process (e.g., where in Blender it appears) and prerequisites (e.g., Blender must be open). Given that an output schema exists (though not detailed), the absence of return value details is acceptable but the tool feels minimally documented.

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?

Despite 0% schema description coverage, the description adds meaningful examples and acceptable values for each parameter (e.g., asset_type: 'hdris, textures, models'; resolution: '1k, 2k, 4k'; file_format: 'gltf, fbx for models'). This significantly aids the agent in understanding parameter usage.

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 action ('Download and import'), the resource ('Polyhaven asset'), and the destination ('into Blender'). The tool name itself indicates the source (Polyhaven), distinguishing it from sibling tools like download_sketchfab_model. No ambiguity.

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 provided on when to use this tool versus alternatives (e.g., search_polyhaven_assets first, or when not to use it). There is no mention of prerequisites or context for selection.

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