compras_pncp_contratacao_itens

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

No annotations are provided, so the description carries the full burden. It discloses a 15-minute cache behavior and lists the endpoint, which gives structural insight. However, it does not explicitly state the read-only nature, pagination behavior, error handling, or the shape of results. The cache note adds value but other behavioral traits are missing.

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 short: one main sentence, one endpoint line, one cache note. The endpoint line is likely unnecessary for an AI agent but not overly verbose. The cache note is a useful behavioral detail. The entire description is front-loaded and efficient, though the endpoint detail could be omitted without loss.

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, 3 required, and an output schema, the description is minimal. It does not explain what information the returned items contain, how to use pagination effectively, or how the required parameters identify a specific contract. Given the existence of an output schema, the return structure is assumed documented elsewhere, but the description lacks context for usage.

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 baseline is 3. The description adds no additional meaning beyond the schema; the endpoint line mirrors the required parameters but does not explain their semantics or how they relate (e.g., that they form a composite key). No extra context is provided for 'pagina' or 'tamanho_pagina' beyond what is 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 clearly states 'Lista itens de uma contratação no PNCP', which is a specific verb ('Lista') and resource ('itens de uma contratação'). It distinguishes from siblings by specifying 'no PNCP', differentiating it from tools for other procurement systems (e.g., 14133). However, it does not explicitly contrast with similar item-listing tools like compras_contratacoes_14133_itens_por_contratacao or compras_arp_itens_listar.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusion criteria for when to prefer this over sibling tools that also list items for contracts. The agent must infer usage solely from the tool name and brief purpose.

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