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

The description discloses that it returns details, and optionally includes items and resultado blocks. It does not mention side effects or errors, but read-only behavior is covered by annotations. The added context about the reference from pncp_buscar is helpful.

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 two sentences, direct, and contains no unnecessary information. It is well-structured and easy to parse.

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 5 parameters and no output schema, the description covers the main purpose and the optional behavior. It does not describe the return format or error conditions, but these are not critical given the simplicity.

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 description goes beyond the schema by explaining that cnpj+ano+sequencial is the reference from pncp_buscar, and clarifies the meaning of the boolean flags itens and resultado. This fully documents the parameter semantics.

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 retrieves complete details of a licitação/contratação using CNPJ, ano, and sequencial, and references the source (pncp_buscar). This is specific and distinguishes it from siblings.

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?

It explains the effect of the optional parameters itens and resultado, which is useful. It does not explicitly state when to prefer this over other tools, but the purpose is clear enough that usage is implied.

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