delete_task

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

No annotations are provided, so the description carries the burden. It clearly indicates the action is permanent ('permanentemente') and a mutation, plus the need for confirmation. However, it does not disclose potential side effects or irreversibility beyond the confirmation step.

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 concise sentence in Spanish with a parenthetical. It is front-loaded and contains no unnecessary words.

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?

Despite having 12 parameters, the description only addresses the confirm parameter. It does not clarify that many parameters (like status, agent_id, phone) are likely not needed for deletion, leading to potential confusion. With no output schema or annotations, the description is incomplete for an agent to use 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 coverage is 100% (all 12 parameters described), so baseline is 3. The description only adds context for the confirm parameter but does not explain the usage of other parameters (e.g., status, agent_id) which seem irrelevant for deletion. It adds minimal value beyond the 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?

The description clearly states that this tool permanently deletes a task and requires confirmation. It uses a specific verb ('Eliminar'), identifies the resource ('tarea'), and distinguishes it from sibling tools like create_task, update_task, and list_tasks.

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 explicitly mentions that confirmation is required by setting confirm=true to execute. It provides clear context on how to use the tool, though it does not explicitly state when not to use it or list alternatives.

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