Remove Task

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

No annotations are provided, so the description must fully disclose behavior. It states delete is permanent, but the schema's 'resolution' field description says delete is recoverable for 30 days, creating a contradiction. The description also omits details about authorization requirements or side effects beyond what is mentioned.

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 relatively concise (three sentences) and front-loads the main purpose. It could be slightly tighter but contains no unnecessary fluff.

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?

Given the tool's moderate complexity (two-step flow) and absence of output schema, the description explains the basic flow and consequences but lacks details on the conflict response structure, error conditions, or how it fits among siblings like 'purge_item'.

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% and schema descriptions are adequate, but the description adds valuable context about the two-step process and what happens on first call. This enriches understanding beyond the raw schema.

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 removes tasks by archiving or deleting, and distinguishes between the two effects. However, it does not explicitly differentiate from sibling tools like 'purge_item' or 'restore_item', which might overlap in functionality.

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 explains the two-step interaction (first call returns conflict, then pass mode) but lacks guidance on when to use this tool instead of alternatives like 'complete_task' or 'purge_item'. No explicit when-not or comparative context is provided.

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