drop_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that a task is dropped, implying a mutating action, but it does not say whether this permanently deletes the task, whether it is reversible, or what state the task enters. For a destructive operation, this is a significant gap.

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 a single concise sentence, front-loaded with the core verb. There is no redundant content. While it is short, it includes the essential differentiating phrase 'without completing it.'

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?

An output schema exists, so return values are covered. However, for a mutating tool with no annotations, the description is too thin: it does not state the outcome for the task, whether it is removed from open lists, or any side effects. The tool's behavior and effects on task state are not adequately specified.

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 0% and the description does not mention task_id. Although the parameter name and title are self-explanatory, the description adds no additional meaning beyond the schema. It fails to compensate for the missing parameter documentation.

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 states a specific verb 'drop' and resource 'task', and the clause 'without completing it' differentiates it from complete_task. However, 'drop' is somewhat ambiguous—it could mean delete, cancel, or abandon—so it could be slightly more explicit about the exact operation.

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?

The description implies the appropriate use case: removing a task without marking it complete. It implicitly excludes complete_task, but it does not explicitly mention alternative sibling tools or spell out when not to use this tool. The context is clear enough for most agents.

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