Ver Metadados de Tabela SIDRA

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds context about the return content, specifically that it includes category IDs and ready-to-use values for the 'classificacao' parameter. It does not detail output structure, but provides meaningful value beyond annotations.

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 three sentences, front-loaded with the main purpose, followed by a clear usage directive and an args line with examples. No redundant or filler content.

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?

Despite having no output schema, the description comprehensively lists what the metadata includes (variables, classifications, territorial levels, periods) and the exact use-case for querying. This is sufficient for an agent to decide when to call it and what to expect.

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?

The input schema describes tabela_id as 'Código da tabela SIDRA', and the description adds practical examples ('9514', '1419', etc.). This gives format guidance beyond the schema's minimal description, helping the agent construct correct input.

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 'Retorna metadados completos' and lists concrete outputs: variáveis, classificações com IDs, níveis territoriais, e períodos. It clearly distinguishes itself from the sibling ibge_sidra_consultar_tabela by focusing on metadata retrieval.

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?

Explicitly states when to use the tool: 'Use SEMPRE antes de ibge_sidra_consultar_tabela quando não souber os IDs de variável ou classificação', naming the alternative tool and the exact scenario. It also notes that it returns the exact classificacao values ready for use, reinforcing its role as a preparatory step.

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