detalles_contratos

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the 10-id cap, duplicate deduplication, the partial-failure contract (non-numeric ids land in 'faltas' while the rest still process), and per-item 'ok' flags. It stops short of auth/rate-limit or ordering guarantees, but the operational semantics are unusually well covered.

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 scoping sentence is front-loaded, followed by clearly labeled Args/Devuelve sections. Every line is information-dense, though the return-value prose is slightly long and could be tightened.

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 and no annotations exist, so the description supplies the return shape itself ('ok', 'detalles' with per-item fields, 'faltas', 'nota'). For a two-parameter batch tool this is complete enough to invoke correctly.

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 description coverage is 0%, so the description must compensate, and it does: 'ids' is documented as a list of numeric id_contrato values with dedup behavior and a 10-per-call cap, and 'maximo' is bounded to 1..10. Both parameters gain meaning not present in the bare schema.

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+resource: batch retrieval of contract details ('Lote de DETALLES de contratos publicados en UNA llamada'). It explicitly distinguishes itself from the sibling detalle_contrato, so an agent can route between the batch and single-item tool without opening either schema.

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?

Gives explicit when-to-use ('evita repetir detalle_contrato por cada id') and a clear when-not/alternative ('usa detalle_contrato si solo necesitas uno'). The condition that selects each tool is spelled out rather than implied.

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