delete_task

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

The description does not disclose whether deletion is permanent or reversible, what permissions are required, or any cascading effects. Since no annotations are provided, the description carries the full burden of behavioral transparency, and it fails to deliver.

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 concise at one sentence, but it sacrifices substance. For a destructive tool, more information is warranted.

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 and the lack of annotations, the description is grossly inadequate. It does not cover return value, side effects, or any behavioral context.

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?

With 0% schema description coverage, the parameter task_id is completely undocumented in both the schema and the description. The description adds no information about the format, source, or constraints of 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 action ('Delete') and target resource ('a task'), making the tool's purpose straightforward. However, it does not differentiate from related tools like complete_task or archive_project, which could also modify task state.

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 delete_task versus alternatives like complete_task, snooze_task, or archive_project. The description lacks any context about prerequisites or exclusions.

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