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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds genuinely new context: it runs exclusively under the connected Gover account and its API permissions, it warns never to pass credentials/auth identity as arguments, and it discloses that large results are truncated and must be fetched via gover_ler_resultado. The statement that it does not alter business records is redundant with the 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 purpose is front-loaded in the first sentence and the remaining sentences are short, discrete directives. One sentence ('Os campos seguem o contrato da API') is filler boilerplate, but overall the text is compact and scannable.

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?

There is no output schema, and the description does cover the critical post-call behavior (resultadoId hand-off for large results) plus auth constraints. Still, for a nested required object at 0% schema coverage it never explains how to build the form or which identifier to supply, leaving a real gap for correct invocation.

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% and the single required parameter is a nested object with three undocumented fields (opcaoId, clienteId, departamentoId). The description only says 'Os campos seguem o contrato da API', which adds no meaning about what any field is or which ID is expected, despite the title promising lookup 'por ID'.

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 states a specific verb (Consultar) plus resource (departamento) and scope (por ID), which distinguishes it from the list/search sibling gover_pesquisar_departamentos. It does not, however, explicitly name any sibling, so differentiation from gover_alterar_departamento or gover_consultar_unidade is left to inference.

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?

Two conditional directives are given: use gover_ler_resultado with the returned resultadoId for extensive results, and fill new payment data only on the Gover portal. However, nothing tells the agent when to pick this tool over gover_pesquisar_departamentos or where the departamentoId is supposed to come from.

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