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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real value beyond them: it accepts POST/PUT/PATCH with the same parameters in JSON or form, and every 400 response carries `exemplo` and `doc`. That is meaningful behavioral context an agent can act on.

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 long opening sentence front-loads what the tool returns, followed by the search mechanism, the method/alias behavior, and the error shape. It is dense but every sentence carries information, with only mild redundancy in the extended first clause.

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?

With 8 parameters, no output schema, and safety already covered by annotations, the description compensates well by describing the return payload (median, range, volume, value, groups) and the group-switching mechanism. It stops short of explaining limits or pagination behavior, but nothing critical is missing to invoke it.

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 coverage is 100% so the baseline is 3, but the description goes further by documenting parameter aliases (`query`/`termo`/`busca`/`search`→`q`, `estado`→`uf`, `limit`→`limite`) and clarifying that `quantidade` is the quantity you will sell. This meaning is not present in the schema.

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 states a specific verb (searches awarded results by item description) and enumerates the response content in detail: result count, median, p25/p75 range, volume bought, and value for quantity. An agent can distinguish this from siblings like search_tenders or who_supplies, though it never explicitly names a sibling.

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?

Usage is implied rather than stated: the 'free summary' framing and the note that other groups can be switched by asking for product+unit hint at when to use it, but there is no explicit when-to-use/when-not guidance or named alternative for a competing tool.

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