Obtener Licitación por Código

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

No annotations are provided, so the description carries full burden. It describes the retrieved data (items, dates, amounts, buyer, award, status) and implies a read-only operation ('obtiene el detalle'). It does not discuss side effects, permissions, or potential errors, but the read nature is clear.

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?

Two concise sentences with no wasted words. The first sentence states the primary purpose, and the second adds format details and return data overview. Information is front-loaded effectively.

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 the absence of an output schema, the description adequately outlines return fields (items, dates, amounts, etc.) and code format. It lacks error information or rate limits, but for a simple retrieval tool, it provides sufficient context for an AI agent to understand the scope.

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 baseline is 3. The description adds value by explaining the code format in context and listing the types of returned information, which supplements the schema's parameter descriptions.

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 tool retrieves the complete detail of a specific procurement (licitación) by its unique code. The verb 'Obtiene' and the resource 'licitación específica por su código único' are specific. Among siblings like 'buscar_licitaciones' (search), this tool is distinct as it targets a single known entity.

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 the code format and what information is returned, implying use when a specific code is known. It does not explicitly state when not to use or suggest alternatives, but the context of sibling tools (e.g., 'buscar_licitaciones') makes the intended usage clear.

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