delete_task

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description does add one real piece of behavioral context — that the task's output is removed too — but says nothing about irreversibility, cascade effects, or authorization requirements.

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?

Two short sentences, front-loaded with the action and its side effect, with the endpoint as supporting detail. No filler, though the endpoint syntax is low-value for an agent that already has the schema.

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, no-output-schema tool, the definition covers the core action and the output deletion but omits confirmation requirements, what happens to dependent objects, and how to choose between this and delete_global_task. Adequate to call safely only because annotations carry the destructive flag.

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%, so the description must compensate, and it only partially does: the path template 'DELETE /project/{project_id}/tasks/{task_id}' clarifies that both integers are path segments rather than body fields. It adds no constraints, formats, or validation notes beyond that.

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?

States a specific verb and resource ('Deletes task'), plus a distinguishing scope detail ('including output') that a bare 'delete' would not convey. It does not differentiate from the sibling delete_global_task, so an agent cannot tell which deletion path applies from this text alone.

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 statement of when to use this versus delete_global_task / delete_project / stop_task, and no prerequisites or warnings beyond the word 'Deletes'. The agent must infer everything from the name.

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