List Help Center Categories

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, so the description does not contradict them. However, it adds no behavioral details beyond the basic action, such as pagination behavior, ordering, or effects of omitting parameters. Given the low annotation burden, the description fails to provide additional 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 very concise with two short sentences, front-loading the main action. However, it omits necessary details about parameters and usage, making it slightly incomplete. It earns a high score for brevity but loses a point for missing 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?

Given the lack of schema descriptions, no output schema, and 3 parameters, the description is insufficient. It does not explain pagination or response format, which is critical for a list tool. The presence of sibling list tools further necessitates clearer guidance.

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 only explains the 'locale' parameter, missing the 'page_size' and 'cursor' parameters. With 0% schema description coverage, the description should compensate but covers only 1 of 3 parameters, leaving pagination semantics undocumented.

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 lists Help Center categories with an optional locale filter. The verb 'list' and resource 'categories' are specific, and the description distinguishes from sibling tools like list_articles or list_sections by naming the resource. However, it does not explicitly differentiate when to use this over similar list tools.

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 only mentions optional locale filtering but provides no guidance on when to use this tool versus other listing tools (e.g., list_sections, list_articles). There is no mention of exclusions or alternative tools, leaving the agent without context for selection.

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