Delete a Task

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

The annotations already declare destructiveHint=true and readOnlyHint=false, covering the safety profile. The description adds the explicit 'cannot be undone' warning, which goes beyond just 'destructive' and indicates irreversibility, providing useful behavioral context for the agent.

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, well-structured sentence that front-loads the action ('Permanently delete') and provides essential warning ('cannot be undone') without wasted words. It is appropriately concise for a simple delete operation.

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 delete operation with one parameter, the description adequately conveys the core behavior and the permanent consequence. No output schema exists, so no return value explanation is required. While it could mention idempotency or error handling, the description is complete enough given the tool's 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?

The input schema fully describes the only parameter, task_id, with a description 'Task ID', achieving 100% schema coverage. The tool description adds no additional parameter-specific meaning, so it relies on the schema's documentation, warranting the 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?

The description explicitly states 'Permanently delete a Planner task', providing a clear verb (delete) and resource (Planner task). The warning 'This cannot be undone' reinforces its destructive nature, distinguishing it from sibling tools that update or retrieve tasks.

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 clarifies that this tool is for permanent deletion, implying it should be used only when the task should be removed permanently. However, it does not explicitly mention alternatives or when NOT to use it, such as using update_task for modifications, so it has clear context but no exclusions or alternative naming.

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