faostat_list_bulk_downloads

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

With no annotations, the description carries full burden. It notes files are 'very large', which is a key behavioral trait, but lacks disclosure on rate limits, authentication, pagination, or response format. The behavior is partially transparent but incomplete.

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 extremely concise: two sentences plus an Args block. The key purpose is front-loaded, and no unnecessary words are present. Every sentence adds value.

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 output schema exists, the description doesn't need to detail return values. However, for a tool listing large files, it lacks context on download process, limits, or link availability. It is adequate but not fully comprehensive.

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 coverage is 0%, so the description must compensate. It explains domain_code with examples (e.g., 'QCL', 'TM') and lang with default 'en', adding meaning beyond the schema's bare titles and types. However, it does not list valid lang values or provide more domain code details.

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 verb 'list', the resource 'bulk download files for a domain', and specifies they are ZIP/CSV archives containing the full domain dataset. This distinguishes it from sibling tools that retrieve data subsets or codes.

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 full domain downloads but does not explicitly state when to use this tool vs alternatives, such as faostat_get_data for smaller data queries. No when-not-to-use guidance or mention of alternative tools.

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