obtener_detalle_compra

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

No annotations are provided, so the description bears full burden. It discloses a critical behavioral trait: detailed quotes are only shown from the 'Cerrada' state on the second call onward. This adds significant value beyond a simple read operation.

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 front-loaded with the core purpose in the first sentence, then lists included details concisely. The behavioral note is appropriately placed. A minor improvement would be bullet formatting for the list.

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 detail-retrieval tool with one parameter and no output schema, the description covers all major aspects: process, products, suppliers, budget, delivery, order status, sustainability flags, and a behavioral note. It is comprehensive enough for an agent to understand what the tool returns.

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 input schema already describes the 'codigo' parameter with format and example. The description adds 'por su código único' but no additional semantics beyond the schema, consistent with high schema coverage.

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 verb 'Obtiene' (gets) and resource 'detalle completo de una Compra Ágil específica', identifying the unique code as identifier. It distinguishes from sibling tools like 'buscar_compras_agiles' (search) and 'obtener_detalle_orden_compra' (purchase order detail).

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 a specific purchase detail is needed by its code, but provides no explicit guidance on when to use vs. alternatives (e.g., searching vs. detail retrieval) or when not to use the tool.

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