delete_task

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

The description lacks any behavioral disclosure beyond the action of deletion. It does not state whether deletion is permanent, soft, or if there are side effects (e.g., on recurring events). With no annotations, the description carries full burden but fails to provide crucial safety or behavior details.

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 (3 words) but lacks structure such as bullet points or separation of concerns. It is front-loaded but too minimal to provide adequate context. While concise, it sacrifices clarity for brevity.

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 has 4 parameters and an output schema, the description is incomplete. It does not explain the return value, required permissions, or the effect of optional parameters. The description provides insufficient context for proper 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?

The input schema has 75% description coverage, so the schema already documents most parameters. The description 'Delete a task' adds no additional meaning beyond the schema. Baseline of 3 applies as schema covers most semantics.

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' clearly states the verb and resource, distinguishing it from sibling tools like 'delete_event' or 'bulk_delete_tasks' through the resource name. However, it does not explicitly specify that it deletes a single task, which could cause confusion with 'bulk_delete_tasks'.

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 usage guidelines are provided. The description does not mention when to use this tool over alternatives (e.g., single vs bulk deletion) or any prerequisites or conditions. This leaves the agent without decision context.

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