Buscar Órdenes de Compra

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

With no annotations, the description carries full burden. It discloses default behavior, automatic date range, and non-filterable status. However, it does not mention rate limits, pagination, or authentication details beyond the ticket parameter description in the schema.

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 well-structured, front-loads the main purpose, and every sentence adds distinct information. It is detailed but concise given the complexity of the tool.

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 is provided, and the description does not explain the return structure (e.g., list of OCs, pagination). It gives status codes but lacks completeness about what the response contains, which is important for a search tool.

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%, so baseline is 3. The description adds value by explaining interaction between parameters (e.g., no date with org/proveedor triggers 30-day search) and providing example values. It repeats some schema info but provides behavioral context.

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 it searches for purchase orders in Mercado Público (ChileCompra). It specifies the default behavior (returns today's OC without parameters) and distinguishes itself from sibling tools like buscar_licitaciones by focusing on purchase orders.

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?

Provides explicit guidance on when to use parameters: without optional params returns today's OC; filtering by date, status, supplier, organization; automatic 30-day search when org/supplier is given without date; lists valid estado values and notes that 'en proceso' appears in response but is not filterable.

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