list_categories

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

With no annotations, the description carries the behavioral burden. It discloses caching behavior via force_refresh ('Bypass cache and fetch fresh data') and implies a read-only operation through 'Browse' and 'fetch.' It does not discuss rate limits or authentication, but for a simple listing tool this is adequate transparency.

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 compact and front-loaded: a one-sentence purpose, a one-sentence usage recommendation, then a clear Args list. Every line earns its place and there is no redundant or repetitive content.

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, an output schema exists to describe return values, and the description covers usage positioning, parameter semantics, and caching behavior, nothing important is missing for an agent to select and invoke this tool correctly.

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 0%, but the description fully compensates by explaining each parameter: subdomain is the Help Center hostname with an example, locale is an optional filter, and force_refresh means bypassing cache. This adds real meaning beyond the raw schema properties.

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 states a specific action and resource: browsing a Zendesk Help Center's structure including locales, categories, and section counts. It also positions itself as the recommended first call to understand available content, which helps distinguish it from sibling tools like list_sections or get_articles.

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?

It explicitly says 'This is the recommended first call to understand what content a Help Center offers,' giving clear usage context. It does not explicitly list exclusion cases or name alternative tools, but the first-call framing strongly implies this should precede more specific queries.

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