Delete Task

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds valuable context beyond annotations by stating 'permanent' and 'cannot be undone,' which aligns with the destructive hint. No contradictions.

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 very concise, consisting of two short, front-loaded sentences. Every sentence adds value: one states the usage, the other warns about destructiveness. No wasted words.

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?

Given the low complexity (1 parameter, no nested objects, output schema present, annotations covering destructive behavior), the description is complete. It covers purpose, usage, and behavioral caveats adequately.

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% and the parameter 'id' has a description in the schema ('The task ID to delete permanently'). The tool description does not add extra parameter semantics beyond what the schema provides, warranting a baseline score of 3.

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?

Purpose is clearly stated: permanently delete a time entry. The verb 'delete' and resource 'time entry' are specific. The tool name 'task_delete' and sibling tools (e.g., absence_delete, project_delete) further differentiate this from other 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 explicitly says 'Use this when the user wants to permanently delete a time entry,' providing clear context. It does not explicitly list alternatives or when not to use, but the warning about destructiveness helps guide usage.

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