search_polyhaven_assets

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

No annotations provided, so the description must disclose behaviors. It mentions returning a list with basic information but omits details on rate limits, authentication, or side effects. The user_prompt parameter is described as telemetry but not elaborated.

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?

Description is brief and structured with a main action followed by parameter explanations. No fluff, but could be more concise by merging parameter details with schema if schema were richer.

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 no output schema or annotations, the description is adequate but lacks detail on return format or pagination. For a simple search tool with optional params, it covers basics but leaves ambiguity about 'basic information.'

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%, so the description compensates by listing all three parameters and explaining asset_type options (hdris, textures, models, all), categories as optional comma-separated, and user_prompt as telemetry. Adds meaning beyond schema defaults.

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 'Search for assets on Polyhaven with optional filtering,' specifying the action and resource. It differentiates from sibling tools like download_polyhaven_asset and search_sketchfab_models.

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 guidance on when to use this tool versus alternatives like search_sketchfab_models. Does not mention context or exclusions, leaving the agent without clear decision criteria.

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