drop_task

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

The description indicates a state change ('dropped/cancelled') but lacks details on whether it's reversible, permissions required, or effects on related tasks. With no annotations, the description fails to disclose behavioral traits sufficiently.

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?

A single, clear sentence with no filler. Every word contributes to understanding.

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 tool with one parameter and no output schema, the description is adequate but could include more context like error conditions or examples. Sibling tools suggest this is a standard mutation, but completeness is minimal.

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 covers the single required parameter 'id' with a description. The tool description does not add further context (e.g., format, constraints), so it adds minimal value beyond the schema.

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 uses clear verb 'Mark' and resource 'task', specifying 'dropped (cancelled)' which distinguishes it from siblings like 'delete_task' (permanent removal) and 'complete_task' (finished).

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?

Description implies the tool is for cancellation, but does not explicitly contrast with alternatives or state when not to use it (e.g., vs. delete or complete). No prerequisites or exclusion conditions.

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