delete_task

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

No annotations provided, so the description carries full burden. It discloses irreversibility ('cannot be undone') and SAFE_MODE restriction. This is adequate for a deletion tool, though it could mention permissions or cascading effects.

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 sentences with a warning emoji, no fluff. Every sentence earns its place: purpose, irreversibility, safety, and restrictions.

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 (1 param, no output schema), the description covers purpose, behavior, safety, and restrictions. It doesn't explain what happens to associated data (e.g., subtasks), but given the tool's simplicity, this is acceptable.

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 taskId description already. The description adds safety rationale ('Requires explicit task ID to prevent accidental deletions'), which adds value beyond the schema by clarifying why the parameter is critical.

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 verb 'delete' and resource 'task', and includes a warning emoji for emphasis. It distinguishes from sibling tools like delete_achievement by specifying 'task from your LifeUp app' and adding 'permanently'.

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 explicitly requires a task ID to prevent accidental deletions and notes the tool is blocked in SAFE_MODE, giving clear when-to-use context. It does not compare to alternatives like archiving, but 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.