Obteniendo detalle del contrato

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

Since there are no annotations, the description provides comprehensive behavioral transparency. Specifically, it states that the URLs provided in the output are 'descarga directa del PDF (sin token),' which is a critical operational detail for the agent.

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?

Although detailed, the structure (using 'Args:' and 'Devuelve:') is highly efficient. Every sentence adds specific value regarding scope, prerequisites, or expected output structure, justifying the length.

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?

The definition is maximally complete. It details the scope of the input, lists nearly every nested resource the tool retrieves (disputes, actions, guarantees), and explicitly defines the structure and behavior of the complex return data.

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 0%, so the description must compensate. It successfully clarifies that `id_contrato` is a specific reference to a published contract and provides a concrete example ID format, greatly improving parameter understanding.

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 purpose is extremely clear: to provide the 'Detalle COMPLETO' of a published contract. It specifies the resource type (contract) and the scope of the detail, clearly differentiating it from simpler list/search tools listed in the siblings.

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 provides specific guidance on how to acquire the necessary input parameter (`id_contrato`), stating that it should come from `buscar_contratos` or `contratos_expediente`, which is invaluable for routing and prerequisite knowledge.

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