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

Annotations already declare readOnly/idempotent/non-destructive, so the description goes further by disclosing auth constraints ('Nunca informe credenciais ou identidade de autenticacao' as arguments) and that new payment data must be entered only on the Gover portal. These add real operational context beyond the structured hints, though it restates 'nao altera registros' which overlaps the readOnly hint.

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?

Reasonably front-loaded, with the key capability stated first and routing/security notes after. However, 'Os campos seguem o contrato da API' is filler that adds no information, weakening an otherwise tight description.

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, so the description should carry return-value context; it partially does by mentioning the resultadoId and the gover_ler_resultado follow-up for large result sets. It remains thin on what the panel returns and which filters matter, leaving the definition only adequate for a 7-param, undocumented-schema tool.

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?

Seven optional params with 0% schema coverage, and the description compensates only with the vague 'Os campos seguem o contrato da API'. It never explains what termo, cidadeId, clientId, unidadeId, funcionarioId, tipoCentroDeCusto, or finalidadeViagemId filter, so the agent gets no semantic grounding for the filters it must supply.

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 ('Consultar') and resource ('painel do usuario autenticado'), with the scope qualification that it uses only the connected Gover account. It is clear what the tool does, though it does not articulate how it differs from the many other 'consultar_*' siblings.

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 routes the agent to gover_ler_resultado for extensive results ('Para resultados extensos, use gover_ler_resultado com o resultadoId retornado'), which is a genuine usage hint. However, it never states when this panel consult is preferred over alternatives, nor prerequisites beyond the implied connected account.

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