bookshelf_bulk_delete_queue

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

The description adds a DESTRUCTIVE warning, but this is redundant with the destructiveHint annotation. It does not explain what exactly is deleted, how the query parameters affect behavior, or whether the operation is irreversible. Minimal value beyond annotations.

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 short but poorly structured. 'Bulk delete queue bulk' is awkward and redundant. The query parameter list and DESTRUCTIVE note are abrupt and not integrated meaningfully.

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?

Given the tool's complexity (5 parameters, destructive operation, bulk behavior) and no schema descriptions, the description is insufficient. It does not clarify what the bulk delete does to the queue, how flags interact, or what the response will be.

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 merely lists parameter names (removeFromClient, blocklist, skipRedownload, changeCategory) without explaining their effect. It also omits the 'body' parameter and uses different casing than the schema, adding confusion rather than semantic clarity.

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 bulk delete action on a queue, which is a specific verb+resource. It distinguishes from sibling tools like bookshelf_delete_queue (singular) and bookshelf_grab_queue_bulk. However, the phrasing 'Bulk delete queue bulk' is redundant and slightly confusing.

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?

There is no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or prerequisites. The destructive nature is implied but not tied to usage decisions.

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