Consultar Períodos Disponíveis de uma Tabela SIDRA

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds behavioral context by specifying the return format (AAAA, AAAAMM, or trimestre), which is useful beyond the annotations. No contradiction with 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 concise and well-structured: a one-sentence purpose statement, a usage directive, a compact Args list, and a Returns line. Every sentence adds value, no fluff or repetition.

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?

For a simple single-parameter tool with no output schema, the description fully covers what the tool does, when to use it, and what it returns. It even explains the benefit of avoiding errors, making it self-contained for an agent.

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 already has 100% parameter coverage with examples. The description supplements this by tying specific example codes to well-known datasets ('1419' para IPCA, '9514' para Censo), adding real-world meaning to the parameter beyond the 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 the tool's purpose: 'Retorna todos os períodos disponíveis para uma tabela SIDRA' with a specific verb and resource. It also distinguishes itself from the sibling tool ibge_sidra_consultar_tabela by noting this should be used beforehand.

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?

It explicitly directs use 'ANTES de ibge_sidra_consultar_tabela' when needing to know available years/months, and cites the benefit of avoiding 'período não encontrado' errors. This provides clear when-to-use guidance and distinguishes it from alternatives.

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