astrax_tarea_limpiar

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

With no annotations, the description carries the full behavioral burden. It discloses what is destroyed (state file and temporary screenshots), which is valuable, but it omits whether the deletion is irreversible, whether confirmation is required, or any permission or rate-limit constraints. Adequate but incomplete for a destructive 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 a single, front-loaded sentence with a parenthetical clarification. Every word earns its place, and there is no filler or redundancy. Slightly less than perfect because the parenthetical could be integrated more smoothly.

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?

Given the tool's simplicity (no parameters, output schema present), the description provides sufficient context: what it deletes and when to use it. It does not need to explain return values, but it could mention potential side effects on task state. Overall adequate for correct invocation.

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 tool takes zero parameters, so the schema description coverage is irrelevant. Per the rubric, zero parameters sets a baseline of 4, and the description does not need to add parameter semantics beyond what the empty schema provides.

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 ('Borra') and resources ('archivo de estado y las capturas temporales'), and clarifies the intent with 'descartar o cerrar una tarea'. This distinguishes it from siblings like astrax_tarea_guardar or astrax_tarea_completar_paso, though the differentiation is not explicit in the text.

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 parenthetical '(descartar o cerrar una tarea)' implies usage context—cleanup when discarding or closing a task. However, it does not explicitly state when to use this versus alternatives like completing steps or saving, nor does it provide exclusions or prerequisites.

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