delete_task

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

With no annotations provided, the description fully carries the behavioral burden. It discloses soft-delete behavior, 30-day retention, the lack of list/restore endpoints, irreversibility, and cascading deletion of comments, labels, and assignees. This is exceptionally transparent.

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 front-loaded with the core action and uses every sentence to convey essential risk information. The wording is efficient and memorable without being padded.

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 single-parameter destructive tool with no output schema, the description covers everything an agent needs to call it safely: irreversibility, retention behavior, lack of restore, confirm-id guidance, and cascading effects. Nothing critical is missing.

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 0% and the description does not explain task_id beyond 'confirm the id first.' That is a safety caution, not parameter semantics. However, the single integer parameter is self-evident from its name, so the lack of explanation is only a minor gap.

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 opens with 'Delete a task,' a specific verb and resource that clearly distinguishes this from sibling deletion tools like delete_comment, delete_bucket, and delete_label. The scope is unambiguous and immediately understandable.

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 gives clear operational context: this is irreversible, the id should be confirmed first, and deletion cascades to associated objects. It does not explicitly name an alternative tool, but none is truly relevant for deleting a task, so the guidance is sufficient.

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