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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the permanent removal and the cascading effect on assignee links, which are important behavioral consequences beyond just 'delete task'. This is concise but informative, revealing destructive scope without unnecessary detail.

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 extremely concise at two short sentences, immediately front-loading the core action and key consequence. Every word contributes: 'permanently' signals irreversibility, and 'all assignee links are removed' clarifies scope without redundancy.

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 simple tool with one parameter and no output schema, the description is complete. It explains what gets deleted, the permanent nature, and the cascading effect on links. No additional return value explanation is necessary as the schema and semantics are straightforward.

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 already describes the single parameter task_id as 'Task ID to delete' with 100% coverage. The description adds no additional parameter-level semantics beyond what's in the schema, but it does clarify the behavioral effect on the task entity, which is sufficient for a simple one-parameter tool.

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 states the action 'Delete a task permanently' with the specific resource (task) and a key nuance (permanently), which distinguishes it from update or unassign operations. It also notes the additional scope of removing assignee links, further differentiating it from simpler delete operations.

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 implies when to use this tool (when you want to permanently remove a task) but does not explicitly contrast it with alternatives like update_task or unassign_task. It gives no explicit exclusions or 'when not to use' guidance, though the phrase 'permanently' offers a caution about its irreversible nature.

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