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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-reading nature is covered. The description adds useful context about the data source (NZ open data catalogue) and the all_fields behavior, but does not disclose default field sets or pagination semantics beyond the schema's existence.

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 one concise sentence that front-loads the core purpose and adds a single actionable tip. There is no fluff or redundant 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 simple listing tool with an output schema present, the description provides a solid context: what it lists, from where, and a key parameter hint. It does not explain return formatting (output schema covers that) and limit/offset are intuitive, so overall it is complete enough for its 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 0%, so the description must compensate. It explains all_fields (true returns names and descriptions) but does not clarify limit or offset parameters, which are left to inference from examples. This is a partial gap in parameter documentation.

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 uses a specific verb ('list') and resource ('thematic groups/categories') tied to the NZ open data catalogue, clearly distinguishing it from sibling tools like group_show (which would show a single group) and tag_list/organization_list (which list other entity types).

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 all groups but does not explicitly contrast with alternatives like group_show. The tip 'Pass all_fields=true' offers a usage hint, but no explicit when-not-to-use or alternative references beyond what the name conveys.

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