bulk_delete_items

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

With no annotations, the description usefully discloses the destructive safety gate ('Requires confirm=true') and an audit behavior ('ids are logged when confirmed'). However it omits the crucial traits of a destructive bulk operation: irreversibility, permission requirements, behavior on partial failure, and any batch-size or rate limits.

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?

Two short sentences with zero waste; the concurrency scope, the confirm gate, and the logging side effect are all front-loaded and each sentence carries information an agent needs.

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 need no explanation, and the confirm/logging details are present. But for a destructive bulk mutation with no annotations and zero schema descriptions, the definition is not complete enough: it lacks reversibility, permission, and partial-failure context an agent needs before firing it.

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%, so the description must carry parameter meaning. It explains only 'confirm' (must be true); board_id and item_ids – including whether all ids must belong to the given board or any count limit – are undocumented anywhere, so the coverage gap is largely uncompensated.

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?

States a specific verb and resource ('Delete many items concurrently'), which is distinguishable from the single-item sibling delete_item by the word 'many'. It does not name an alternative explicitly, so it stops short of full sibling differentiation.

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?

Usage is only implied by 'many items' – an agent can infer this is for batches rather than single deletes, but there is no explicit statement of when to prefer this over repeated delete_item calls, nor any exclusions or preconditions beyond the confirm flag.

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