delete_task

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

Describes the operation as 'Destructive' and notes potential confirmation, which is helpful with no annotations. However, lacks details on side effects (e.g., subtask behavior, permanent deletion) and does not explain the confirm_token parameter.

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?

Extremely concise: 4 short lines plus parameter docs. Every sentence serves a purpose, no redundancy. The main action is front-loaded.

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 essential behavior and parameter semantics partially, but given the presence of an output schema (not shown), the description could be more complete on return values and error conditions. Missing documentation on confirm_token is a gap.

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?

Documents uuid and dry_run with clear descriptions, adding value beyond schema. However, fails to mention confirm_token, which is a third parameter in the schema. Schema coverage is 0%, so description should cover all parameters; missing one reduces score.

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?

Clearly states 'Delete a task from Taskwarrior' with a specific verb and resource. The note 'Prefer completing over deleting' explicitly distinguishes it from the sibling complete_task.

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 advises preferring completion over deletion, giving a clear when-not-to-use. Also mentions potential confirmation requirement, but does not list other alternatives like archiving or all scenarios.

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