delete_task

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

With no annotations provided, the description carries full burden for behavioral disclosure. It adds valuable context by specifying 'soft delete' (implying reversible/non-destructive deletion), but doesn't cover permissions needed, confirmation prompts, side effects, or what happens to associated data. The disclosure is partial but meaningful.

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?

Extremely concise at just 4 words, front-loaded with the core action, and every word earns its place by adding critical information ('soft delete'). No wasted words or redundant phrasing.

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 destructive operation with no annotations and no output schema, the description is minimally adequate. It identifies the tool as a deletion operation and specifies it's 'soft', but lacks details on permissions, confirmation, return values, or error conditions that would be helpful for safe invocation.

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 single parameter 'id' well-documented as 'Task ID to delete'. The description doesn't add parameter details beyond what the schema provides, but with only one parameter and complete schema coverage, baseline 4 is appropriate as minimal additional value is needed.

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 action ('Delete') and resource ('a task'), making the purpose immediately understandable. However, it doesn't differentiate from sibling 'update_task' regarding deletion vs modification, nor does it mention what distinguishes it from potential hard-delete alternatives.

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 like 'update_task' for status changes or potential archive operations. The description mentions 'soft delete' but doesn't explain when this is appropriate versus other deletion methods or what the implications are.

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