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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description goes further by disclosing the result-size escape hatch (gover_ler_resultado), forbidding credentials/auth identity as arguments, and bounding new payment data to the Gover portal. These are real operational traits not present in the structured fields. It stops short of stating rate limits or what a large-result truncation looks like.

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, which is good, but the remainder is a sequence of loosely connected boilerplate sentences mixing auth policy, contract notes, pagination, and payment policy. Each sentence is short yet the whole reads as a policy dump rather than a focused tool definition.

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 no output schema, the description reasonably covers auth scope, result handling via resultadoId, and the payment-data boundary, which is enough for an agent to invoke it. The remaining gap is that three fully undocumented optional parameters leave the caller guessing about valid inputs.

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%, so the description carries the full burden, and it only partially compensates. It implies data and localizador are acceptable lookup keys but says nothing about their format, whether they are mutually exclusive, or what clienteId scopes. One of the three parameters is entirely unaddressed.

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 (voo), plus the two retrieval keys (localizador or data), which lets an agent distinguish it from search tools like gover_buscar_voos or gover_cotar_voos. However, it never explicitly names which sibling it replaces for a lookup-by-identifier flow, e.g. gover_consultar_localizador_aereo.

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?

Provides one concrete routing rule: for extensive results, use gover_ler_resultado with the returned resultadoId. That is a genuine alternative-with-condition. But there is no guidance on when to prefer this tool over gover_consultar_localizador_aereo, gover_consultar_resultados_voos, or gover_consultar_minhas_viagens, so usage is only partially implied.

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