download_polyhaven_texture

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

Annotations set readOnlyHint: true, but the tool actually downloads and writes files (dest_dir), which is a write operation. This contradiction severely misleads about behavior. Additionally, no disclosure of file overwrites, permissions, or network usage.

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?

Single sentence packs many details, but is somewhat long. Structurally front-loaded with the main action and key parameters. Could benefit from breaking into two sentences for clarity.

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?

Covers essential parameters and output usage, but misses details on dest_dir behavior and does not mention return values. Annotations are contradictory, reducing trust. Adequate but with 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?

With 0% schema coverage, the description adds substantial meaning: examples for asset_id, valid resolution options ('1k'/'2k'/'4k'/'8k'), and format choices ('png'/'jpg'). It also implies dest_dir usage, though not fully specified.

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 downloads CC0 PBR texture sets from Poly Haven and classifies maps (baseColor, normal, roughness, etc.). It provides specific examples for asset_id, resolution, and format, and distinguishes from siblings by detailing the Unity integration.

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 implies use when needing CC0 PBR textures for Unity, but does not explicitly state when to avoid it or mention alternatives like 'download_pbr_material' or 'search_polyhaven_textures'. Guidance is partial.

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