compras_contratacoes_14133_consultar

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

The description explicitly states that it returns 'detalhes completos' listing several fields (objeto, valor estimado, modalidade, instrumento convocatório, status no PNCP) and mentions the cache duration of 15 minutes. No annotations are provided, so this description carries the full behavioral transparency burden – and it does so well.

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 three short, focused sentences. The first states the core purpose, the second provides the endpoint for reference, and the third lists the return contents and cache behavior. No fluff, all essential information front-loaded.

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 the tool has only one parameter (fully described), an output schema exists, and the description covers purpose, parameter semantics, detailed return fields, and caching policy, the description is complete enough to enable correct use without requiring additional context.

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?

The schema coverage is 100% and the description adds context by mentioning that id_contratacao is the internal id returned by listar_contratacoes_14133, which links the parameter to a sibling tool's output. This goes beyond the raw schema definition, providing operational semantics.

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 the action (consultar uma contratação 14.133), the resource (pelo id interno), and lists the details returned (objeto, valor, modalidade, etc.). It distinguishes the tool from siblings like compras_contratacoes_14133_listar (which lists, not queries by id) by mentioning that it uses the internal id returned by the list endpoint.

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 usage when you have an internal id from listar_contratacoes_14133, and the schema reinforces that id_contratacao is required. However, it does not explicitly exclude alternative tools (e.g., when you might use other consult tools) or provide negative examples, but the context is clear enough for the target use case.

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