Move Task to Trash

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

Annotations already indicate destructiveHint=true and readOnly=false. The description adds valuable context that this is recoverable (soft delete), not final deletion, and requires confirmation. It also specifies only active tasks can be moved, which is a useful behavioral constraint.

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 compact sentence with an upfront confirmation warning. It conveys the key facts without wasted words.

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 single-parameter tool with no output schema, the description covers the core behavior (soft delete to Trash), recoverability, and the active-task constraint. It doesn't mention cascading effects on subtasks, but given the simplicity, this is acceptable. The absence of output schema reduces the need to describe return values.

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 schema provides only task_id as a required UUID with no description. The description adds minimal parameter semantics by referring to 'an active Task', implying task_id identifies the task to trash, but does not explicitly document the parameter or any constraints beyond 'active'.

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 tool moves an active Task to Trash as a recoverable soft delete, using a specific verb and resource. It distinguishes from archive_task (archive vs trash) and restore_task (inverse), and clarifies it is not final deletion.

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 implies this is for soft-deleting active tasks by moving them to Trash, but it does not explicitly state when to use this over archive_task or other alternatives. It does note it's not final deletion, but doesn't name alternatives or exclusions.

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