Buscando laudos

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

With no annotations, the description carries the full burden. It does add real behavioral context: the default sort ('ordena por fecha DESC'), 10 rows per page, and a 1..6 limit on consecutive pages. It says nothing about permissions, rate limits, or failure behavior, which an unannotated mutation-adjacent fetch tool should ideally cover.

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?

Front-loads the purpose before the Args/Devuelve blocks, and each documented argument and the return dict earn their place given the 0% schema coverage. It is dense but not padded.

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 exists, so the description supplies the return shape ({'ok','ses','modo','total','paginas','pagina','tamano_pagina','filas'}) and notes that sumilla is COMPLETA relative to buscar_resoluciones. Combined with full parameter documentation, an agent has enough to invoke and read results 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 entirely, and it does: every one of the 9 parameters is documented, including the anio catalog ('2026'..'1998' or '1982'), the exact-word requirement with a cross-reference to buscar_palabras_clave, and the full set of 'orden' values with their default.

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 and resource ('Busca resoluciones de ANULACION y EJECUCION DE LAUDOS ARBITRALES') and ties it to the 'Comerciales' searcher, which is more precise than the bare name. It hints at differentiation via 'la sesion es del buscador de laudos' but never explicitly tells the agent why to pick this over the sibling buscar_resoluciones.

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?

Usage is implied through mechanism rather than stated: 'ses' is described as the session for the next page, and palabra_clave points to buscar_palabras_clave for obtaining the exact keyword. There is no explicit when-to-use/when-not guidance or named alternative against which this tool competes.

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