compras_pesquisar_preco_servico

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

No annotations are provided, so the description carries the burden. It discloses the endpoint and contrasts with a consolidated view, implying raw price output. However, it does not mention behavioral traits like pagination, ordering, or any side effects. The output schema exists but is not referenced. Transparency is moderate.

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 description is extremely concise: two sentences. The first sentence states the purpose, the second provides the endpoint and key usage guidance. No redundant information, front-loaded, and every sentence is necessary.

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?

Given the tool has 8 parameters (1 required) and an output schema, the description is adequate. It explains the main purpose, endpoint, and directs to an alternative for consolidated data. It doesn't cover prerequisites or limitations, but the schema and output schema fill some gaps. Slightly above baseline.

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 100%, so the parameter descriptions are fully provided in the schema. The description adds no additional meaning beyond the schema, e.g., it does not explain that 'codigo_item_catalogo' is the CATSER code or how to find it. Baseline 3 is appropriate.

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 description clearly states the tool searches for service purchase prices (CATSER), with a specific verb 'Pesquisa' and resource 'preços praticados em compras de serviço'. It distinguishes from sibling 'compras_pesquisar_preco_material' by specifying service, and contrasts with the consolidated alternative 'compras_pesquisar_precos_para_etp'.

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 explicitly tells when not to use this tool by directing to the alternative 'compras_pesquisar_precos_para_etp' for consolidated statistics. It lacks guidance on when to use other siblings like 'compras_detalhar_preco_servico', but the main alternative is clearly stated, providing good context.

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