verificar_orden_compra

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

Since no annotations are provided, the description carries the full burden. It explains the tool's workaround behavior: consulting process details and cross-referencing with the Órdenes de Compra API. It does not mention permissions or side effects, but the behavior is clearly described for a verification tool.

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 sentences with no redundant information. The key limitation is highlighted using 'IMPORTANTE', making it easy to scan. Every sentence adds value.

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 single parameter and no output schema, the description adequately covers the tool's purpose and behavior. It could be improved by specifying the output format (e.g., boolean or OC id), but it is still complete for the tool's complexity.

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 only parameter (codigo) is fully described in the schema, but the description adds value by providing the required format with an example (XXXXXX-YYY-COTXX), which helps agents construct correct inputs.

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's purpose: verifying whether a specific 'Compra Ágil' has an issued purchase order. It includes a specific verb (verifica), resource (Compra Ágil), and output (OC emitida). This distinguishes it from sibling tools like 'obtener_detalle_compra' and 'obtener_detalle_orden_compra'.

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 explicitly warns that the API's 'oc_emitida' status does not work in practice, advising agents to use this tool instead. While it does not list all alternatives, it provides clear context for when to use this tool over other methods.

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