delete_task

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds no further behavioral context such as whether deletion is permanent, whether related records are affected, or what happens if the task ID does not exist. No contradiction, but no added value beyond the 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 one-sentence description is short but under-specified. It does not earn its place because it only restates the tool name, providing no additional information. This is under-specification rather than effective conciseness.

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?

While annotations and schema cover the destructive, idempotent nature and the single parameter, the description lacks usage guidance and any clarification of deletion semantics (e.g., hard vs soft delete). Without an output schema or behavioral notes, the description is insufficient for an agent to confidently invoke the tool.

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 description coverage is 100%, with the task_id parameter fully documented as an integer with a description. The tool description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 'Delete a task' is essentially a sentence-form restatement of the tool name and title, adding no new information. It does state the action and object, but it fails to differentiate from the many sibling delete_* tools or provide any detail about what deleting a task entails beyond the name itself.

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 no guidance on when to use this tool versus alternatives like update_task, get_task, or search_tasks. It lacks any preconditions, exclusions, or mentions of alternative operations, leaving the agent with no context for appropriate selection.

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