task.delete

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

No annotations are provided, so the description carries the full burden. It merely restates the tool name without revealing critical behavioral traits such as whether deletion is permanent, side effects on related data, or permission requirements. For a destructive operation, this lack of transparency is a significant risk.

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 short, but it simply restates the tool name ('deletes a task') and does not use the space to provide any additional value. This is under-specification rather than conciseness, as the sentence fails to earn its place by adding context.

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 destructive nature, the description is insufficiently complete. It does not mention reversibility, impacts on related items, or any conditions that must be met before deletion. While the parameter count is minimal, the absence of behavioral context leaves the description incomplete.

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?

The schema already fully describes the only parameter (id) with a basic type and description. The tool description adds no new meaning, but with 100% schema coverage, a baseline score of 3 is appropriate. No additional context is needed for the parameter itself.

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 the resource 'task', which is specific and distinguishes it from sibling tools like task.create, task.get, and task.update_status. Despite being terse, it unambiguously communicates the tool's core function.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or contexts where deletion is appropriate. Sibling tools like task.complete or task.update_status are not referenced, leaving an agent without direction for selecting the right operation.

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