Verificar Orden de Compra

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds substantial behavioral context: the verified API limitation, that it avoids API calls to save quota, the reuse-from-detail strategy, and the critical caveat that 'sin OC' does not prove absence. This is exactly the kind of extra disclosure annotations cannot carry.

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?

Front-loads the core purpose, then the limitation warning, then the strategy — logical ordering. It is long, but nearly every sentence carries decision-relevant information; only minor tightening is possible without losing the caveats.

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?

No output schema exists, so the description carries the return-semantics burden and does so by explaining what the result means and — importantly — what a negative result does not prove. Complete for an agent to call it correctly and interpret the outcome.

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 coverage is 100% and the single parameter (codigo) is fully documented in the schema with format and example. The description adds no parameter-level syntax or semantics beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb+resource (informs whether a Compra Ágil has an issued purchase order by reading id_orden_compra from the detail), and explicitly distinguishes itself from siblings by noting it does NOT query the API on its own but reuses the detail from obtener_detalle_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?

Explicitly says when to use it (only as a re-read of an already-fetched detail, otherwise just points to how to confirm in the public record) and names the alternative tool (obtener_detalle_compra). It also warns when NOT to expect a confident result, avoiding wasted quota.

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