Resultado por município

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

No annotations are provided, so the description carries the full burden. It adds the useful qualifier 'parcial oficial' (partial, official tally) but says nothing about pagination (limite default 20), turno/year defaults, or whether results change over time as the count is finalized.

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?

Two short sentences plus a concrete example, front-loaded with the purpose. Efficient, though the example only reinforces what the first sentence already implies.

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?

An output schema exists, so return values need no explanation. However, for a 6-parameter, 3-required query tool with zero annotation and zero schema coverage, the description leaves most parameters and all usage guidance undocumented.

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% across 6 parameters, so the description must compensate. It documents seulement 'municipio' (exact name, 7-digit IBGE code, or TSE code), leaving uf, cargo, ano, turno and limite completely unexplained in both schema and description.

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?

States a specific verb+resource: it returns the official partial result for a cargo within a municipality. It is clear what the tool does, but it does not distinguish itself from the sibling 'resultado' (also a result tool) or explain how it differs from 'resumo_brasil' / 'listar_eleicoes'.

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?

There is no indication of when to use this tool versus 'resultado', 'resumo_brasil' or 'listar_eleicoes'. The example invocation shows syntax but not the selection condition, so the agent must infer scope from the name alone.

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