get_polyhaven_categories

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'Get', which is reasonable, but it omits details such as authentication requirements, rate limits, error conditions, or output structure. For a simple list retrieval, this is adequate but minimal.

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 sentence stating the tool's purpose followed by a parameter list. No unnecessary words; the most important information is front-loaded. Every sentence is justified.

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 the tool's simplicity (one parameter, no output schema), the description covers the core functionality and parameter meaning adequately. It lacks output format details, but the phrase 'list of categories' implies an array response, which is sufficient for this 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 input schema has no description for the only parameter (asset_type), so the description adds significant value by explicitly listing allowed values ('hdris, textures, models, all') and explaining the parameter's role. This compensates well for the schema's lack of detail.

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's action ('Get') and resource ('list of categories') with a specific scope ('for a specific asset type on Polyhaven'), making its purpose straightforward. However, it does not explicitly distinguish itself from sibling tools like search_polyhaven_assets or download_polyhaven_asset, which slightly limits differentiation.

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 provides no guidance on when to use this tool versus alternatives. It implicitly suggests using it when categories are needed, but lacks explicit context, exclusions, or comparisons to sibling tools, leaving the agent without decision support.

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