weeek_delete_task

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the bar is lower, yet the description still adds real value: it clarifies the operation is irreversible and distinct from completion ('removed, not just completed') and that a confirmation flag is mandatory. It stops short of covering permissions, failure modes for a bad id, or cascading effects on subtasks/comments.

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 tight sentences, front-loaded with the destructive action, then the guard condition, then the alternative. Every clause earns its place with zero 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?

For a two-parameter delete tool with no output schema, the description covers purpose, irreversibility, confirmation, and the sibling alternative. Only minor gaps remain, such as behavior when the id does not exist or permission requirements.

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 50%: confirm is self-documenting via its const/description, while id has no schema description. The description only implies id semantics via 'by id' and does not add format or validation detail. Baseline 3 is appropriate given the schema carries the confirm constraint.

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?

Specific verb (permanently delete) and resource (a WEEEK task), plus the scoping qualifier 'by id'. It explicitly contrasts itself with the nearest sibling, weeek_complete_task, so an agent can disambiguate without reading either 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?

States the precondition ('Requires confirm:true') and names the alternative tool with the condition that selects it ('to merely close a task use weeek_complete_task instead'). This is exactly when-to-use / when-not-to-use guidance.

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