search_polyhaven_assets

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions the return type ('list of matching assets with basic information') but omits side effects, authentication needs, rate limits, or whether the search is read-only. This is inadequate for a tool with no annotation safety net.

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, with a clear front-loaded purpose statement and a structured parameter list. Every sentence is informative, and there is no superfluous text.

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 tool's simplicity (2 optional parameters, no output schema), the description is minimally sufficient. However, it lacks details on pagination, result fields, or error handling, which would improve usability for an agent without context.

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 schema only provides types and defaults (0% schema coverage). The description adds critical meaning: allowed values for 'asset_type' (hdris, textures, models, all) and clarifies 'categories' as a comma-separated list. This significantly enhances parameter understanding beyond the raw 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 action ('Search for assets on Polyhaven') and identifies the resource ('assets on Polyhaven'). It also mentions optional filtering, distinguishing it from sibling tools like 'get_polyhaven_categories' and 'download_polyhaven_asset'.

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 does not provide any guidance on when to use this tool versus its siblings (e.g., for broad search vs. category browsing). It lacks context about prerequisites or scenarios where alternatives are preferred.

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