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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the permanence framing ('Cannot be undone'), but says nothing about cascading effects (subtasks, comments, relations) or permission requirements, which are the real unknowns 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?

Two short sentences plus a minimal args block; the destructive nature and the argument are front-loaded with zero filler.

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 and annotations covering destructiveness, the essentials are present. It is still thin on side effects and error/permission behavior, which matters when deletion is irreversible.

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% and the schema only says the field is a string, so the description must compensate. It does by specifying that task_id is a UUID of the task to delete, which is meaningful format information beyond the schema.

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 (delete) and resource (task), and adds the 'standalone' qualifier that separates it from procedure/entity deletion and from task-completion siblings. It stops short of naming an alternative tool, so it is clear but not fully differentiated from siblings like complete_task or update_task.

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 word 'standalone' implies a constraint on what may be deleted, which is implied usage guidance. However, it never says when to delete versus complete/update a task, nor what happens if the task is not standalone.

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