Exportando a Excel

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

With no annotations, the description carries the full burden and does well: it discloses the return payload keys, that output is base64 to be decoded and saved as .xls, and importantly the cap behavior (ok:false with size and a reduction hint, NEVER truncating the file). It omits auth/permission needs and rate limits, but error and output 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?

Front-loads the purpose, then cleanly separates Args and Devuelve. The return-value block is dense but earns its place given no output schema exists; no filler sentences.

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 one-parameter tool with no output schema and no annotations, the description supplies purpose, parameter provenance, return shape, and error/cap behavior. Nothing essential to calling it correctly is missing.

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 by defining 'ses' as the session returned by buscar_resoluciones or buscar_laudos. That tells the agent where the required value comes from, which is the key semantic gap the bare string schema leaves open.

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 ('Exporta la BUSQUEDA ACTUAL de la sesion a EXCEL (XLS) en base64') and anchors it to the site's 'Exportar' button. This clearly distinguishes it from the search/list siblings (buscar_resoluciones, listar_salas, etc.), which are all read/query tools rather than exporters.

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 establishes usage context by noting it exports the CURRENT session search and that 'ses' comes from buscar_resoluciones or buscar_laudos, which routes the agent to run a search first. It stops short of explicit when-not-to-use guidance or naming alternatives, but for a single export tool the context is clear.

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