producao_anual

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

No annotations provided. Description only lists parameters and examples, but does not state that it is read-only, idempotent, or any side effects. Lacks behavioral context.

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?

Description is concise, uses bullet points for products, and clearly separates args. Efficient but lacks some detail.

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?

Has output schema but description does not explain return format (e.g., units, per-state data). Given no annotations and low schema coverage, it leaves significant gaps for an agent to know how to interpret results.

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%. Description adds list of allowed crop names for 'produto' and notes default year for 'ano' (previous year), but 'ano' default in schema is 0, which may be ambiguous. Provides some value beyond schema but incomplete.

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?

Clearly states it provides historical annual crop production by state from IBGE PAM. Lists example products. Distinguishes from siblings like estimativa_safra (estimate) and preco_diario (price), but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, limitations, or recommended contexts.

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