Delete task

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'deletes a task' without disclosing that the operation is destructive, requires a confirmation string, or might be reversible. It also does not mention idempotency. This is a significant gap for a mutation tool.

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, short sentence, which is concise, but it is so sparse that it provides minimal value. It is not front-loaded with the most critical information (e.g., confirmation requirement). While not verbose, it under-specifies to the point of being nearly useless.

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 destructive tool with required parameters and no annotations or output schema, the description is severely incomplete. An agent would not know that 'confirm' must be 'DELETE', that task_id is required, or what the response looks like. The description does not enable correct invocation.

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 description coverage is 0%, meaning the schema provides no property descriptions, and the tool description mentions none of the parameters. The required 'confirm' parameter (a safety gate) and the optional idempotency_key are completely unexplained. The description fails to compensate for the schema's lack of documentation.

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 action (deletes) and the resource (a task), making the purpose unambiguous. It does not differentiate from sibling tools, but no sibling performs deletion, so the verb+resource is sufficient. A higher score would require explicit scope (e.g., permanent vs. soft delete), which is absent.

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?

There is no guidance on when to use this tool versus alternatives like update_task_status or restore_task. It does not mention that deletion is destructive, that confirmation is required, or that it might be reversible via restore_task. The description provides no context for selection.

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