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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds meaningfully beyond them: it reveals the cascade behavior ('Also deletes all of its subtasks') and the permanence ('this cannot be undone'). This tells the agent exactly what will be destroyed, which is exactly the kind of behavioral context that annotations do not convey.

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 imperative sentence with an em-dash addition. It front-loads the core purpose ('Delete a task') and packs the most important caveats (subtask cascade, irreversibility) into a short, scannable string. No filler or redundant phrasing.

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 one-parameter destructive tool with annotations already covering the safety profile and the schema describing the parameter source, this description is complete. It adds the missing behavioral specifics (cascade, irreversibility) and needs no further explanation of return values or permissions. An agent can invoke it correctly and anticipate the consequences.

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 100%, so the schema already documents that taskId identifies the task from list_standalone_tasks or get_standalone_task_by_key. The tool description adds no parameter-specific meaning, but with full schema coverage the baseline of 3 is appropriate; the schema does the necessary 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?

The description starts with a specific action and resource: 'Delete a task.' It also notes the cascade to subtasks, which further distinguishes this from sibling delete tools (e.g., delete_standalone_attachment, delete_standalone_comment) by specifying the affected entity and its nested content. The resource and operation are unambiguous even without opening the schema.

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 explicit when-to-use or when-not-to-use guidance relative to alternatives. It does not mention other deletion tools, conditions, or prerequisites, leaving the agent to infer usage from the name and schema. The only contextual cue is the irreversibility warning, which is more behavioral than a usage guideline.

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