Delete a task

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

Annotations already signal destructive, but the description adds crucial behavioral detail: permanent deletion, soft-delete visibility window with show_deleted=true, cascading to subtasks, and the response shape. This goes well beyond what the annotations convey.

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 dense but every sentence adds a distinct fact: permanence, distinction from completion, soft-delete behavior, cascading, and return value. It is front-loaded with the most decision-relevant information.

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?

Covers the destructive semantics, the alternative tool, the observable side effects, and the return value. With a destructive operation and no output schema, this description gives an agent everything needed to call it 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?

The input schema has 100% description coverage, so both parameters are already self-documenting. The description adds no param-specific meaning, but the schema carries the full burden; baseline 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?

States the exact operation ('Deletes a task permanently') and immediately distinguishes itself from complete_task, so an agent can tell the two apart. The resource and effect are unambiguous.

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?

Explicitly says when NOT to use it ('this is NOT the same as completing it') and names the correct alternative ('use complete_task instead'). Also discloses cascading deletion of subtasks, giving clear selection guidance.

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