remove_task

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

With no annotations, the description carries the full burden. It reveals an important execution guarantee: 'Resolve-all then drop (indexes do not shift),' along with the claim that multiple deletions happen in 'one write.' This is meaningful behavioral context beyond the schema, though it does not address irreversibility or failure modes.

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?

Three short sentences with no wasted words. It front-loads the primary action, then gives concise addressing guidance, then a key behavioral guarantee. Every sentence earns its place.

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 7-parameter deletion tool with no output schema and no annotations, the description covers core deletion semantics and batch resolution behavior, but it omits the role of the required 'version' parameter and any expected result or error context. The schema compensates partially, but overall completeness is only minimally sufficient.

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 86%, so the baseline is 3. The description's 'pass indexes or tasks' largely restates the schema's addressing-mode descriptions. It adds no further detail on the required 'version' parameter or the optional 'expect' guard.

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 and resource: 'Delete one or many tasks in one write.' It also clarifies scope and batch capability, clearly distinguishing this from siblings like complete_task, reopen_task, and update_task which are non-destructive.

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 explicit when-to-use or alternatives are named. The verb 'Delete' makes the core context obvious, and 'For several, pass indexes or tasks' guides addressing mode, but the description does not say when to prefer this tool over siblings or when to avoid it.

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