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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds meaningful extras: it uses only the connected Gover account's API permissions, requires no credentials as arguments, and points to the resultId handoff pattern. That is real added value, though it never describes result shape or pagination limits beyond the pointer.

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 with the purpose, which is good, but the paragraph mixes useful routing (gover_ler_resultado) with off-topic policy text about new payment data being entered only in the Gover portal that does not help an agent call this 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?

A 7-parameter tool with no output schema, 0% parameter documentation, and no explanation of the return contract. The description gestures at the resultId delegation pattern but leaves most of what an agent needs to populate the call unspecified.

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 coverage is 0% across 7 parameters, so the description carries the full burden and largely fails it. 'Os campos seguem o contrato da API' is a non-answer: termo, cidadeId, clientId, unidadeId, funcionarioId, tipoCentroDeCusto and finalidadeViagemId are never explained, and only the city scoping is implied by the title.

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 clear verb+resource ('Pesquisar bairros') scoped by city, which fits the naming contract. However, it does not distinguish itself from closely related siblings such as gover_buscar_cidades_hotel or gover_buscar_referencias_hotel, leaving the agent to infer the boundary between city-level and neighborhood-level lookups.

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 routes the agent to gover_ler_resultado with the returned resultId for extensive results, which is genuinely useful. But it gives no explicit when-to-use/when-not guidance relative to the neighboring search tools, and the closing sentence about payment data is unrelated to invocation.

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