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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the endpoint and the fact that either idCompra or PNCP control number is accepted. It does not disclose auth requirements, rate limits, pagination edge behavior, or response structure, but the annotations lower the burden here.

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 concise sentences with no filler. The main purpose is front-loaded, and the identifier-format note adds useful invocation detail. Every sentence earns its place.

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?

The rich schema, detailed parameter descriptions, output schema, and annotations mean the agent has enough to invoke the tool correctly. The main gap is the absence of explicit routing guidance among the many similar item-listing siblings. Apart from that, no critical calling information is missing.

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 input schema already provides detailed explanations for all four parameters, including format examples and default values. The description largely restates what the schema says about accepted identifiers. It adds the endpoint but little parameter meaning beyond the schema, so the baseline 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 clear verb and resource: 'Lista itens de uma contratação 14.133 específica.' The word 'específica' helps distinguish it from broader listing siblings, and the endpoint is named. However, it does not explicitly contrast itself with sibling tools like compras_contratacoes_14133_itens_listar, so differentiation is implied rather than stated.

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 gives no guidance on when to use this tool versus alternatives such as compras_contratacoes_14133_itens_listar or compras_pncp_contratacao_itens. It only explains identifier formats, which is parameter context rather than usage direction. There are no exclusions, prerequisites, or alternative routing.

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