obter_municipio

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

No annotations are provided, so the description must disclose behavioral traits. It states it 'gets' details, implying read-only, but does not mention authentication, error handling, or other behaviors. For a straightforward ID lookup, this is adequate but not rich.

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?

Single concise sentence directly states the tool's purpose without any unnecessary words. Perfectly front-loaded and efficient.

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?

With an output schema present (as per context signals), the description does not need to explain return values. The tool has one parameter, low complexity, and the description completely covers its role given the context.

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 100%, including an example and format. The description adds no new semantic value beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description clearly states the tool retrieves complete details of a municipality by its IBGE code. Verb 'obtém' and resource 'detalhes completos de um município' are specific, and the method is precise. This distinguishes it from siblings like listar_municipios or buscar_municipios_por_nome.

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 when to use: when a municipality's IBGE code is known and full details are needed. Without explicit exclusions, the context from sibling tools (e.g., buscar_municipios_por_nome for name-based search) offers indirect guidance, but no direct 'when not' is provided.

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