list_categories

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds useful filtering context (parent for subcategories, hide_empty for unused categories) but does not disclose likely return volume, pagination behavior, or authorization requirements. This is acceptable given annotation coverage but no rich additional behavior is revealed.

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?

Three concise sentences, front-loaded with the main purpose. Each sentence adds value: listing, filtering options, and field selection. No redundant or vague text.

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?

For a straightforward read-oriented list tool with 8 parameters, the description covers the key filtering capabilities (parent, hide_empty) and field selection. Pagination and sorting are schema-documented with defaults, so their absence is not critical. It is sufficiently complete for the tool's complexity.

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 description coverage is 100% for all 8 parameters. The description adds semantic meaning beyond the schema: clarifying that 'parent' filters for subcategories, 'hide_empty' skips unused categories, and 'fields' limits response fields. This helps the agent understand why/when to use these parameters.

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 begins with 'List product categories,' which is a specific verb+resource that clearly differentiates it from sibling list tools like list_products or list_tags. It unambiguously states the tool's primary function.

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 listing categories and provides context on filtering (by parent, hide_empty, fields). It does not explicitly mention when to use this over alternatives, but the resource-specific operation is clear given sibling names. No exclusions are needed.

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