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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds only the word 'Permanently', which reinforces rather than extends that signal; it says nothing about cascade behavior (subtasks, tags), required permissions, or whether the call is reversible, which are the remaining 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?

One short sentence, front-loaded with the key warning ('Permanently') and the identifying parameter. No 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?

An output schema exists so return values need not be explained, and the tool is simple (one param). However, for a destructive, non-idempotent operation the description leaves open whether deletion cascades or is confirmable, which is a meaningful gap for an agent deciding to call it.

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% with a single required 'id' parameter, so the schema already carries the parameter meaning. The description restates that the id identifies a task but adds no format, source, or validation detail beyond the schema — the expected baseline when the schema does the work.

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 ('Permanently delete') and resource ('a task by id'), which is unambiguous and distinct from sibling tools like complete_task or update_task. It does not explicitly contrast with delete_tag, but the resource noun makes the difference self-evident.

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 no when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternatives (e.g., whether to archive/complete instead of deleting). The word 'Permanently' hints at irreversibility but is not framed as usage guidance.

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