Detalle de una Orden de Compra

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/profile burden is largely covered. The description adds valuable provenance context (the code must come from an external source and 'id_orden_compra viene null en el 100% de los procesos'), but it does not describe the return format, pagination, or error behavior when a code is invalid.

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 capability, then the critical constraint. The warning is genuinely load-bearing, though the caution is stated twice ('Úsala cuando ya tengas el código por otra vía' and 'No esperes obtenerlo con las demás herramientas'), a mild redundancy that trims efficiency.

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?

For a single-parameter read tool with no output schema, the description covers what is returned (montos, comprador, proveedor, productos), the accepted input formats, and the critical precondition for obtaining the code. An agent has everything needed to call it correctly or recognize it cannot.

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?

With one parameter at 100% schema coverage, the schema fully documents codigo_oc including both accepted formats and examples. The description repeats the dual-format acceptance ('ID numérico o código alfanumérico externo') without adding syntax or validation detail beyond the schema, so the baseline of 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?

States a specific verb and resource (obtener el detalle completo de una Orden de Compra) and enumerates exactly what the detail contains: montos, comprador, proveedor adjudicado y productos adquiridos. It also distinguishes itself from the sibling Compra Ágil tools by clarifying that this is the legacy OC API and a separate data source.

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?

Explicit about when to use it and when not to: 'Úsala cuando ya tengas el código por otra vía' plus concrete sources (la OC emitida como proveedor, un correo, la ficha pública del proceso). It actively warns against expecting this server's other tools to supply the code, which routes the agent away from a dead end.

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