Delete Task

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

With no annotations, the description must carry the full behavioral burden. 'Delete a task' only signals a destructive action; it does not disclose irreversibility, side effects, permissions, soft-delete behavior, or failure semantics.

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, front-loaded sentence with no filler; every word contributes to the core purpose. It is concise, though it sacrifices valuable behavioral context for brevity.

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 one-parameter destructive tool with an output schema, 'Delete a task' plus the schema is minimally sufficient for a correct call. However, the absence of any behavioral or usage context leaves meaningful gaps for an agent deciding whether deletion is permanent or appropriate.

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 the single task_id parameter is already described as 'Task UUID'. The description adds no parameter-level meaning, so the schema fully carries the burden; baseline 3 applies.

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 states a specific verb ('Delete') and a resource ('task'), making the core operation unambiguous and distinct from siblings like create_task or complete_task. However, it adds no scope or nuance beyond the tool name/title, so it does not fully distinguish edge cases like permanent deletion vs. completion.

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 such as complete_task or update_task. No contexts, prerequisites, or exclusions are provided; the agent must infer usage solely from the name.

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