pesquisar_preco

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

With no annotations, the description carries the full burden, and it partially does so by disclosing the return content ('preços praticados em compras públicas'). However it omits permission requirements, pagination behavior, and any indication of result scope or rate limits.

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?

Three short, front-loaded sentences with no filler; the core purpose leads and the parameter guidance follows. Efficiently sized for the amount of content.

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?

An output schema exists, so return values need not be detailed, and the description covers the essential tipo/codigo pairing. It is still incomplete on pagination and on when this tool is the right choice, leaving gaps for an agent.

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 compensate. It clarifies that 'tipo' accepts 'codigoItemCatalogo' or 'codigoPdm' and that 'codigo' is the item code, but leaves 'pagina' and 'tamanho_pagina' entirely 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?

Names a specific verb (Pesquisa) and resource (preços de materiais no catálogo federal), and states it returns prices from public purchases. The purpose is clear, though it does not explicitly distinguish itself from price-adjacent siblings like listar_atas_registro_precos.

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 explains how to call the tool but gives no when-to-use context, prerequisites, or alternatives among the 14 siblings. An agent gets no routing guidance for choosing this over other procurement lookups.

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