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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further: it states the call runs solely under the connected Gover account's API permissions, forbids passing credentials or auth identity as arguments, and explains the large-result handoff to gover_ler_resultado via resultadoId. That adds real auth and pagination context beyond 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 leads, which is good, but several sentences are boilerplate (the credentials warning, the payment-data-in-portal note) that dilute the core lookup guidance. It is not bloated, but not every sentence earns its place for an agent deciding how to call the tool.

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 no parameter documentation, so the description should do more; it does supply the resultadoId pagination handoff, which is valuable. Still missing: what the lookup returns, whether either key is required, and how it differs from the sibling solicitacao readers.

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 must carry the load. It only says lookup is 'por ID ou numero interno' and that 'os campos seguem o contrato da API', without stating formats (integer vs string), that both parameters are optional, or which key to prefer. Two of two parameters remain behaviorally undocumented.

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 (buscar) and resource (solicitacao) with the two lookup keys, matching the title. It is clearly a read-one lookup, but it never names the close siblings (gover_consultar_solicitacao, gover_detalhar_solicitacao_completa, gover_filtrar_solicitacoes) that an agent must choose between in this large tool family.

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?

Gives one useful routing rule: for large results use gover_ler_resultado with the returned resultadoId, and that new payment data must be entered in the Gover portal. However, it never states when to prefer this lookup over gover_consultar_solicitacao or gover_detalhar_solicitacao_completa, so the main selection decision is left implicit.

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