preset_search_polyhaven

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is read-only, authentication requirements, or rate limits. The description only mentions the search action without safety or side-effect information.

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: one line stating the purpose followed by a brief bullet-like breakdown of parameters. No redundant or extraneous 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?

The description lacks information about the return structure or results format, and does not mention that the search results can be used with sibling tools like preset_download_polyhaven for downloading assets. Given the absence of an output schema and annotations, the description should provide more workflow context.

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 meaning beyond the schema by specifying allowed values for asset_type ('hdris', 'textures', 'models'), providing examples for categories (e.g., ['brick'], ['outdoor']), and explaining limit as 'massimo di risultati'. This compensates for the 0% schema coverage.

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 it searches CC0 assets on Poly Haven, and lists the search parameters. However, it does not differentiate itself from the sibling tool preset_search_ambientcg, which searches a different source.

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 for searching Poly Haven assets but provides no explicit guidance on when to use this tool versus alternatives like preset_search_ambientcg or preset_download_polyhaven. No when-not-to-use or exclusion criteria are given.

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