compras_contratacoes_14133_itens_por_contratacao

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to repeat those. The description adds the specific endpoint and clarifies the operation scope, but it does not disclose additional behavioral details such as result ordering, pagination behavior, or response shape; the output schema mitigates this.

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 short sentences with no filler. The core purpose is front-loaded, and the endpoint reference is useful corroborating detail that does not bloat the description.

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 read-only, idempotent paginated listing tool with a complete input schema and an output schema, the description is nearly sufficient. The main gap is the lack of explicit differentiation from the similarly named sibling compras_contratacoes_14133_itens_listar, which could help an agent choose between them with less ambiguity.

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%, and the schema already explains pagination defaults, maximum page size, and that id_contratacao is the internal identifier returned by listar_contratacoes_14133. The tool description itself adds no parameter-level meaning beyond wording the same scope, so the baseline score of 3 is appropriate.

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 action ('Lista itens') and a specific resource ('uma contratação 14.133 específica'), so an agent can tell it is a per-contract item listing operation. It includes the exact endpoint, but it does not explicitly distinguish itself from the similarly named sibling compras_contratacoes_14133_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?

Usage context is implied by 'específica' and by the required id_contratacao parameter, whose schema description says it comes from listar_contratacoes_14133. However, the description gives no explicit when-to-use guidance or comparison against sibling item-listing tools such as compras_contratacoes_14133_itens_listar or compras_pncp_contratacao_itens.

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