weeek_delete_task

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

Even though annotations already mark destructiveHint=true and idempotentHint=false, the description adds important context: it emphasizes irreversibility, clarifies that the task is removed rather than completed, and mandates confirm:true. This goes beyond the annotations to explain the operational consequences.

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 concise sentences, front-loaded with the action ('Permanently delete'), and every clause adds value: irreversibility, the confirm requirement, and the alternative tool. No waste.

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?

The description covers the essential aspects for a simple destructive delete operation: what it does, irreversibility, the required confirmation, and an alternative. It does not mention return values, but there is no output schema, and the operation's outcome is clear. Slight lack of mention of permissions or side effects is acceptable given the annotations and simplicity.

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 50%: the confirm parameter has a description in the schema, while id has none. The description only says 'by id' without adding details about the id parameter's format or source. This is adequate but not compensatory; the confirmation requirement is restated in both places.

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 verb 'Permanently delete' and clearly states the resource 'WEEEK task by id'. It also distinguishes itself from completing a task by explicitly saying 'not just completed', which differentiates it from sibling weeek_complete_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 description gives explicit guidance: it requires confirm:true and directly names an alternative for a less destructive action ('use weeek_complete_task instead'). This clearly tells the agent when to use this tool versus the sibling completion tool.

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