search_polyhaven_assets

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

The description discloses the return behavior (list of matching assets with basic information) and notes that user_prompt is for telemetry. With no annotations provided, the description carries the burden and does a reasonable job, though it doesn't mention any side effects or limitations beyond that.

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 and structured: one-line purpose, parameter list, and return statement. It avoids unnecessary detail and is front-loaded.

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?

The description covers the core functionality, parameters, and return value. Given the tool's simplicity (3 optional params, no output schema, no annotations), it is sufficiently complete for basic use, though it could benefit from mention of related sibling tools or typical use case.

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 provides the meaning of each parameter, including allowed values for asset_type and format for categories. Since schema coverage is 0%, this is the only source of parameter semantics and it does compensate reasonably, though defaults are not mentioned.

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 searches for Polyhaven assets with optional filtering, using a specific verb and resource. This distinguishes 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 implies the tool is for searching assets but does not explicitly state when to use it versus alternatives like get_polyhaven_categories or search_sketchfab_models. No exclusions or alternative recommendations are provided, so guidance is only implicit.

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