search_polyhaven_assets

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

No annotations provided, so description carries full burden. It discloses that filtering is optional and that the return is a list with basic information, but omits rate limits, pagination behavior, or error handling (e.g., empty results).

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?

Well-structured with front-loaded purpose statement followed by parameter details. Given zero schema descriptions, the 'Parameters:' section adds necessary value rather than redundancy. Slightly verbose but efficient.

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?

Adequate for a simple 2-parameter search tool with no output schema—the description explains the return value (list with basic info). However, it misses the opportunity to link to get_polyhaven_categories for valid filter values, which is relevant given the sibling tool exists.

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 coverage is 0% (no property descriptions). The description compensates well by documenting valid enum values for asset_type (hdris, textures, models, all) and explaining the comma-separated format for categories. Loses one point for not referencing get_polyhaven_categories to discover valid category strings.

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?

States specific verb (Search) and resource (assets on Polyhaven), and distinguishes from sibling search_sketchfab_models by explicitly naming the platform. Could be clearer about scope (e.g., CC0 assets only) but adequately describes the core function.

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?

Lacks explicit guidance on when to use versus download_polyhaven_asset or when to call get_polyhaven_categories first to discover valid category values. Mealy describes functionality without workflow context.

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