Delete task

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

The description adds the context 'permanently remove', reinforcing the destructiveHint annotation and implying irreversibility. However, it does not disclose side effects on related data or any confirmation requirements, offering only marginal extra value beyond the annotation.

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?

A single sentence conveys the core purpose without any fluff. It is front-loaded and easy to parse.

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?

While the tool is simple, the description omits critical context about parameter semantics and fails to address when to use this tool over similar ones. The absence of any parameter explanation makes it incomplete for agents unfamiliar with the domain.

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?

Input schema has zero description coverage for the two parameters (ticket and project). The description does not explain what these parameters represent or how they are used, leaving the agent with no semantic understanding beyond parameter names.

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 'Permanently remove a task from its board' uses a specific verb ('remove') and resource ('task'), clearly distinguishing it from sibling tools like update_task (modify) and get_task (read). The term 'permanently' adds clarity that the action is irreversible.

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 guidance is provided on when to use this tool versus alternatives (e.g., archiving or updating task status). The description lacks context about prerequisites, permissions, or scenarios where deletion is inappropriate.

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