delete_task

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

The description adds value beyond the 'destructiveHint' annotation by explicitly stating the action is 'irreversible.' This reinforces the destructive nature and helps the agent understand the permanence. No contradiction with annotations.

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 extremely concise, consisting of two sentences that front-load the key information. There is no redundant or unnecessary text, and every sentence serves a purpose.

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 tool's simplicity (one parameter, destructive operation), the description completely covers the necessary context: what the tool does, its irreversibility, and an alternative for a non-destructive outcome. The presence of an output schema reduces the need for return value explanation.

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?

Input schema coverage is 100%, and the schema already describes the parameter 'task_id' with a clear description. The tool description does not add any additional parameter-specific semantics, so the baseline score of 3 is appropriate.

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 tool's purpose: 'Permanently delete a Todoist task.' It uses a specific verb and resource, and explicitly distinguishes from the sibling tool 'complete_task' by advising to use that alternative if keeping a record is desired.

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 provides clear guidance on when not to use this tool by suggesting 'complete_task()' as an alternative for record-keeping. However, it does not mention other relevant contexts or alternatives among the sibling tools, such as batch updates or moving tasks.

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