list_categories

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

No annotations are provided, so the description should carry the full behavioral burden. 'List' implies a read-only operation and the mention of topic counts suggests aggregate metadata, but the description does not state read-only behavior explicitly, ordering, freshness, or whether the result is static HIG content.

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?

It is a single well-formed sentence that front-loads the action and scope without filler. Every phrase, including 'top-level' and 'with topic counts', contributes useful 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?

For a zero-parameter list tool with no output schema, the description is nearly sufficient: it states the resource scope and the returned content. The main gap is that it does not explain how these categories relate to the sibling list_topics output or what the count values represent.

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 tool has zero parameters, so the baseline is 4. There is no parameter semantics to clarify, and the description appropriately does not invent any.

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 gives a specific verb and resource: it lists top-level categories in the Apple Human Interface Guidelines, and adds that topic counts are included. That is clear enough to distinguish a browsing/list operation, though it does not explicitly contrast itself with the sibling list_topics.

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?

Usage is implied by the word 'List' and by 'top-level categories', but the description does not say when to use this instead of list_topics or search_hig. No exclusions or prerequisites are provided, leaving the agent to infer the navigation role.

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