obtener_detalle_orden_compra

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

No annotations provided, so the description carries the full burden. It discloses that the tool returns information about amounts, buyer, supplier, and product list, implying a read-only retrieval. However, it does not explicitly state side effects, permissions, or other behavioral traits.

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 two sentences, thoroughly informative without unnecessary words. It efficiently conveys the tool's purpose, input, and output, earning its place.

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 a simple tool with one parameter, no annotations, and no output schema, the description adequately explains what it returns (amounts, buyer, supplier, line items). It is complete for its complexity level.

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 has 100% coverage for the single parameter, and the description adds value by explaining that it accepts both numeric ID and alphanumeric code, with an example format (e.g., '1057532-156-AG26'). This goes beyond the schema's description.

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 full detail of a purchase order from Chile's Mercado Público, specifying accepted inputs (numeric ID or alphanumeric code) and output fields (amounts, buyer, supplier, line items). This specificity distinguishes it from sibling tools.

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 order code and need complete details. It does not explicitly state when not to use or provide alternatives, but the context is clear and the input description guides appropriate use.

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