datasaude

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

No annotations provided; description does not explicitly state that the tool is read-only or non-destructive. It implies safe data retrieval but does not cover behavioral traits like caching, rate limits, or error handling.

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?

Well-structured with bullet points and examples. Every sentence is informative, no fluff. Front-loads purpose and provides clear categorization of indicators.

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?

No output schema; description mentions format options ('tabela'/'json') but does not describe the actual return structure, pagination, or error responses. For a query tool, this is a gap.

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 100%, but description adds value with readable indicator names, territorial level codes, and concrete examples (e.g., localidade='35' for SP). Enhances understanding beyond schema.

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 it queries Brazil health indicators via IBGE/DataSUS, lists specific indicators and territorial levels, and distinguishes from sibling tools (which focus on broader IBGE data) by specifying the health domain.

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?

Provides explicit examples and usage patterns (e.g., infant mortality, life expectancy by state). Lacks explicit 'when not to use' or comparison to alternatives like ibge_indicadores, but examples guide effective use.

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