consultar_licitacoes_pr

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the filtering scope and does not disclose pagination behavior, result limits, or data freshness, which is a moderate but not severe gap.

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 a single, front-loaded sentence with no redundant words. It efficiently states the action, resource, and primary filter dimensions in a compact form.

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?

The output schema and annotations cover return values and safety, and the required field ano is identifiable. However, pagination parameters are not explained and there is no guidance distinguishing this tool from the novo_mural siblings, so the description is adequate but not fully self-sufficient.

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?

With 0% schema description coverage, the description needed to clarify all five parameters but only maps three of them: ano (base year), municipio, and trecho do objeto for objeto. The pagination-related parameters limite and deslocamento are left completely unexplained, leaving an important gap for an agent trying to control result size and offset.

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 opens with the specific verb 'Pesquisa' and names the exact resource 'Mural de Licitações', followed by the meaningful filter dimensions: base year, municipality, and object excerpt. This distinguishes it from sibling tools that target different resources such as obras, acórdãos, or the new mural.

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 gives clear context: use this tool to query the Licitações Mural by base year, municipality, and object text. It does not explicitly mention when to prefer it over consultar_novo_mural_pr or other sibling tools, but the intended use is clear even without an explicit exclusion.

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