delete_task

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Delete a task' without indicating whether the deletion is permanent, irreversible, or whether it cascades to subtasks. This is a significant gap for a destructive operation.

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, concise sentence with no wasted words. It is front-loaded with the action and resource. However, it is so minimal that it edges toward under-specification, lacking useful contextual detail without becoming verbose.

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 tool that deletes data, the description is incomplete. It does not explain the consequences of deletion, whether it affects related subtasks, or what response to expect (no output schema). The lack of annotations and output schema heightens the need for richer description, which is absent.

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 input schema fully describes the `id` parameter as 'The task ID to delete' with 100% coverage, so the description adds no additional parameter semantics. The baseline of 3 applies because the schema handles the documentation effectively.

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 identifies the action ('Delete') and resource ('a task'), which is specific and unambiguous. However, it does not distinguish from sibling tools like complete_task or update_task, which could be alternatives depending on the desired outcome. It lacks a note about whether deletion is permanent or a soft-delete.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., task must exist), no scenarios for use, and no exclusions. Sibling tools such as complete_task suggest an alternative workflow, but the description does not address this.

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