get_polyhaven_categories

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states that it retrieves categories and lists possible asset_type values. It does not describe output format, network dependencies, or potential errors, which is insufficient for a tool likely requiring external API calls.

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, consisting of one sentence and a parameter hint. Every word serves a purpose with no redundancy, making it efficient and easy to parse.

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?

While the tool is simple, the description lacks context about what 'categories' are and what the return value looks like (e.g., a list of strings). With no output schema, the agent is left guessing the response format, which could lead to misuse.

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 schema has 0% coverage and no enums. The description adds critical meaning by listing the allowed values for asset_type ('hdris, textures, models, all'), which is not present in the schema. This significantly aids the agent in correct usage.

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 retrieves categories for a PolyHaven asset type, specifying the verb 'Get' and the resource 'categories'. It also lists the possible asset_type values, making the purpose unambiguous and distinct from sibling tools like search_polyhaven_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 provides no guidance on when to use this tool versus alternatives, such as search_polyhaven_assets or download_polyhaven_asset. There is no mention of prerequisites or exclusions, leaving the agent without context for decision-making.

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