compras_uasg_buscar

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

Beyond the readOnly/idempotent annotations, the description reveals that search is executed locally by scanning upstream pages, that results are cached for 24h, that pagination applies after local filtering, and that the payload includes `_busca_local`, `_paginas_varridas`, and `_universo_varrido` to expose truncation. It also documents the upstream `nome` parameter quirk that could cause silent universe-wide results.

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 definition is front-loaded with an excellent one-sentence purpose and uses structured sections, which helps readability. However, it contains changelog noise such as '✅ Restaurada em 2026-08-05', a counterfactual rationale, and repeated cache information that could be condensed into a few concise operational notes.

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?

For a tool with unusual local-search behavior, this description covers performance cost, cache duration, truncation visibility, upstream contract pitfalls, and result filtering semantics. An output schema exists, so the description does not need to enumerate return fields, and the mention of debug payload fields is a useful supplement.

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?

The schema already covers all three parameters, so the baseline is 3. The description adds valuable meaning by clarifying that `pagina` and `tamanho_pagina` paginate the locally filtered result set, not the upstream API pages, which changes how an agent should interpret those parameters.

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 states a specific verb and resource: 'Busca UASGs por trecho do nome (match parcial, ignora acento e caixa).' This clearly distinguishes it from sibling tools like compras_uasg_listar and compras_uasg_consultar.

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 makes it clear that this tool is for searching UASGs by a name fragment, which tells an agent when to call it. It does not explicitly name alternatives or exclusions, but the introductory phrase provides enough contextual guidance for routine selection.

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