Batch remove items

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

The destructiveHint annotation already communicates that this is a destructive operation, and the description's 'Remove' is consistent with that. The description does not add much beyond the annotation except the batch/single-operation scope; it does not mention irreversibility, cascading project deletion, or failure behavior. With annotations present, the bar is lower, so this is adequate but not exceptional.

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 front-loaded sentence with no filler. It names the action, the target resource, and the batching behavior without wasting any words.

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 destructive batch operation, the description is terse, but the rich input schema, destructive annotation, and presence of an output schema cover most operational detail an agent needs. It would be slightly stronger with explicit guidance about using remove_item for single removals, but the tool is otherwise complete enough to select and invoke correctly.

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 100%, and the schema already explains items, itemType, id, name, and dryRun clearly, including the important fallback rule for id vs name. The tool description adds no parameter-level guidance beyond the schema, so the baseline score of 3 is appropriate.

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 a specific verb ('Remove'), a clear resource ('multiple tasks or projects from OmniFocus'), and a scoping qualifier ('in a single operation'). This makes it easy to distinguish from single-item siblings like remove_item and from add/edit batch siblings like batch_add_items and batch_edit_items.

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 phrase 'multiple... in a single operation' clearly indicates when this tool is appropriate: when several items need deletion at once. It does not explicitly name alternatives or state when not to use it, but the batch context is clear enough to guide selection.

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