delete_task

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

The description states 'permanently', indicating irreversibility, which is valuable. However, it does not disclose permissions needed, cascading effects (e.g., on subtasks, comments), or whether it's a hard delete vs. archive. Since no annotations are present, the description carries the burden but only partially fulfills it.

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, clear sentence that conveys the core action. It is concise and front-loaded, with no wasted words. Slightly more context on consequences could improve it without sacrificing brevity.

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 simple delete operation, the description is mostly adequate. However, given the absence of an output schema and annotations, it would benefit from explaining what happens to associated items (e.g., checklists, files) and whether the action is reversible.

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% with clear parameter descriptions. The tool description adds no extra meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 the action ('Delete') and the resource ('a task'), with 'permanently' specifying the scope. It distinguishes from sibling tools like 'delete_task_dependency' or 'delete_bulk_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?

No explicit guidance on when to use vs. alternatives (e.g., remove_task_from_list, delete_bulk_tasks). The simplicity of the operation partially compensates, but better would be to note when not to use (e.g., task already deleted) or permission requirements.

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