delete_task

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

No annotations provided. Description notes the return includes a transaction ID for undo, implying reversibility, but omits auth requirements or whether deletion is permanent/soft.

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?

Concise with clear Args and Returns sections. Could be slightly shorter by removing redundant 'task' prefixes.

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?

Covers return value and parameter descriptions well. However, lacks information about required parameter combinations (at least one identifier likely needed) and behavior on recurring tasks.

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?

All four parameters are explained with their roles (e.g., 'task_name: Task name to search for'), adding significant meaning beyond the schema's type definitions.

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 it deletes a task, a specific verb and resource. It distinguishes from siblings like delete_list and delete_note, but could be more precise about task context.

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?

No guidance on when to use this tool versus alternatives like complete_task or archive_list. Missing prerequisites like task existence.

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