compras_pncp_contratacao_itens

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the endpoint and a 15-minute cache, which is useful context, but it does not describe pagination limits or other runtime behavior; the output schema and parameter descriptions cover much of the rest.

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 entire description is two short, front-loaded sentences with no filler. The endpoint and cache information are directly useful and nothing in the description wastes an agent's attention.

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 that this is a simple read-only list operation with full input schema coverage, annotations, and an output schema, the description is largely sufficient for invoking the tool correctly. The main gap — choosing it over similar sibling tools — is already accounted for under usage guidelines.

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% and each parameter has its own description, so the schema carries the semantic burden. The description's endpoint template reinforces the required path parameters but adds no meaning beyond what the input schema already provides.

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 and resource: 'Lista itens de uma contratação no PNCP', and reinforces it with the endpoint path. It does not explicitly differentiate from similar sibling tools like compras_contratacoes_14133_itens_listar, but the PNCP qualifier clearly narrows the scope.

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 implies when to use the tool: to list items of a PNCP contratação identified by cnpj, ano, and sequencial. However, it gives no explicit conditions or alternatives, and the large sibling list contains many similarly named item-listing tools, so routing guidance is limited to what the name and endpoint already suggest.

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