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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it operates exclusively through the connected Gover account/permissions, must never receive credentials as arguments, and routes large results to gover_ler_resultado. The payment-portal sentence is tangential but the rest is genuinely additive.

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?

Front-loaded and reasonably short, but several sentences are boilerplate that do not help select or invoke this specific tool (the 'new payment data only in the Gover portal' line in particular). Content is serviceable without being tight.

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?

The mention of the resultId/gover_ler_resultado handoff is a useful completeness signal for a search tool with no output schema. But with a nested 11-field form at 0% schema coverage, the definition leaves the actual query semantics undocumented, which is the main thing the agent needs.

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 'form' parameter contains a deeply nested object with ~11 undocumented fields (nome, ativo, pagina, numLinha, clienteId, unidadeId, departamento, codigoInterno, departamentoId, grupoClienteId, opcaoId). The description only hand-waves with 'Os campos seguem o contrato da API', which compensates for nothing.

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 first sentence ('Pesquisar departamentos') essentially restates the title, giving a verb+resource but no real elaboration. It does not differentiate from close siblings like gover_consultar_departamento, gover_departamentos_por_unidade, or gover_pesquisar_unidades, so an agent cannot tell which department-retrieval tool serves which case without opening schemas.

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 supplies one genuine usage rule: for extensive results, use gover_ler_resultado with the returned resultId. It also states the tool does not alter records. However it gives no when-to-use vs alternatives (e.g., consultar_departamento vs departamentos_por_unidade), so routing guidance is only partial.

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