Eliminar tarea

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

No annotations are provided, so the description carries full burden. It discloses the authorization requirement but does not mention behavioral traits like irreversibility, side effects (e.g., cascading deletions), or error conditions. Partial coverage only.

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 two short sentences, front-loaded with the action, and contains no extraneous information. Every word earns its place.

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 2 required parameters, no output schema, and no annotations, the description is minimal. It lacks details on output, error handling, and expected behavior, making it incomplete for a deletion tool.

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 50% (token described, taskId not). The tool description adds no additional meaning beyond the schema. Given low coverage, it should compensate but does not.

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 'Elimina una tarea' (Deletes a task), specifying the verb and resource. It distinguishes from sibling tools like create_task or update_task_status. However, it does not mention whether deletion is permanent or cascading, just slightly reducing clarity.

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 lists a precondition: 'Requiere sesión con rol 'admin'.' This tells when to use (only if admin), but provides no guidance on when not to use, alternatives (e.g., update status), or context for choosing this tool over others.

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