delete_task

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose the return value semantics ('True if deleted, False if not found'), which is useful. However, it omits other behaviors such as whether deletion is permanent, cascading effects, or permission requirements. The disclosed behavior is minimal but non-contradictory.

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 concise and well-structured with clear sections for Args and Returns. Every sentence earns its place; there is no fluff or repetition. It front-loads the core purpose and provides exactly the necessary details.

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 one-parameter delete tool, the description is largely complete: it states the purpose, parameter, and return behavior. No output schema is needed because the return is described. It lacks usage guidelines, but that is already penalized in its own dimension. Given the tool's simplicity, the description covers the essential aspects 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 description coverage is 0%, so the description must compensate. It explicitly explains the only parameter: 'task_id: The ID of the task to delete.' This adds clear semantic meaning beyond the schema's bare type/title, even though the parameter name is fairly intuitive. The description fully documents the parameter.

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 action: 'Delete a task by ID.' It uses a specific verb ('Delete') and resource ('task'), and distinguishes itself from sibling tools like delete_note and update_task. The purpose is unambiguous.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when deletion is appropriate, or any exclusion conditions. The description only states what the tool does, not when it should be invoked.

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