search_polyhaven_assets

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

No annotations are provided, so the description carries the full transparency burden. It only states that the tool 'returns a list of matching assets with basic information,' but does not disclose read-only nature, limitations, failure modes, network behavior, or output shape beyond a vague list.

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 short, front-loaded with purpose, and includes a clean parameter list followed by a return statement. Every sentence earns its place with no redundant or irrelevant 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?

Despite the tool being named 'search,' no query/text parameter exists, and the description does not clarify that search is performed only via asset_type/category filters. It also does not specify what 'basic information' includes, and with no output schema, the agent cannot predict the result structure adequately.

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 description adds critical semantics absent from the input schema: exact allowed values for asset_type (hdris, textures, models, all) and the comma-separated format for categories. Since schema description coverage is 0%, this compensation is essential and effective.

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 opens with 'Search for assets on Polyhaven with optional filtering,' clearly identifying the verb and resource. It distinguishes itself from sibling tools like download_polyhaven_asset and get_polyhaven_categories by explicitly focusing on searching assets.

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 usage when searching Polyhaven assets, but it does not explicitly state when to prefer this over sibling search tools (e.g., search_sketchfab_models) or related category/download tools. No exclusions or alternative guidance is provided, leaving usage context inferred rather than fully explicit.

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