faostat_list_groups

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether the operation is read-only, requires authentication, has rate limits, or any side effects. For a simple listing tool, the omission is significant, especially given the lack of annotation safety signals.

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 brief and front-loaded with the primary action and examples. It includes an Args section explicitly. No extraneous text. However, the parameter description could be integrated more naturally.

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?

The tool has an output schema, so return value details are not required. However, given 9 sibling tools and no annotations, the description omits context like pagination, error handling, or whether the list is exhaustive. It minimally covers the purpose but leaves gaps for a complete understanding.

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 add meaning. It merely restates 'lang: Language code (default: 'en')', which duplicates the schema's title and default. No valid language codes, formats, or constraints are provided, offering little extra value beyond the parameter name itself.

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?

Description states 'List all top-level FAOSTAT data groups' with examples (Production, Trade, Food Security), providing a specific verb and resource. It also notes 'Use this to discover what categories of data are available.' However, it does not explicitly distinguish from siblings like faostat_list_domains or faostat_groups_and_domains, which could be confused for similar operations.

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 gives a use case ('discover what categories of data are available') but lacks guidance on when not to use this tool versus alternatives. No exclusions or references to sibling tools are provided, leaving the agent to infer appropriateness.

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