search_polyhaven_assets

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

The description fails to disclose behavioral traits such as return format, pagination, error handling, or side effects. Since annotations are absent, the description bears full responsibility for transparency, but it only lists input parameters without explaining output behavior or operational constraints.

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 covering purpose and parameter details. It is front-loaded with the verb and resource, and every word adds value. No unnecessary 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?

Given the absence of annotations and output schema, the description leaves significant gaps. It does not explain return values, behavior on no results, or how the tool interacts with siblings like download_polyhaven_asset. Users are left guessing about the tool's full behavior.

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 must compensate. It adds meaning by listing valid values for 'asset_type' (hdris, textures, models, all) and describing 'categories' as a comma-separated list. This aids understanding beyond the schema, but it could further specify where to obtain valid categories (e.g., referencing get_polyhaven_categories).

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 PolyHaven assets') and mentions optional filtering. It lists the two parameters with their allowed values, making the purpose clear. However, it does not explicitly differentiate from sibling tools like download_polyhaven_asset or get_polyhaven_categories, which could cause confusion about when to use this tool.

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives (e.g., get_polyhaven_categories for listing categories, download_polyhaven_asset for downloading). It lacks any contextual cues for when the search is appropriate or what preconditions exist.

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