bookshelf_delete_queue

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

The description repeats the destructive hint from annotations ('DESTRUCTIVE: this deletes data') but adds no new behavioral details. It does not explain side effects like whether the queue item is removed from the client or what happens to associated files. Beyond the redundant warning, there is no disclosure of internal behavior.

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 only two sentences but is under-specified and misleading. It front-loads a vague purpose and mislabels parameters, so the brevity comes at the expense of clarity. The warning is useful but does not compensate for the lack of structural information.

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 operation with five boolean parameters and an output schema, this description is entirely insufficient. It fails to explain what each parameter does, the effect on the queue and client, or the return value. The agent cannot reliably determine the tool's behavior from this description and the bare schema.

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 compensate, but it only lists parameter names in camelCase ('removeFromClient, blocklist, skipRedownload, changeCategory') while the schema uses snake_case ('remove_from_client', etc.) and omits the required 'id'. It also incorrectly labels them 'Query params' when they are body properties, adding no semantic meaning beyond the property names.

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 'Delete queue' which names the resource and verb but is ambiguous about whether it deletes the entire queue or a single queue item. The schema has a required 'id' suggesting per-item deletion, but the description does not clarify this. It also does not distinguish from the sibling tool 'bookshelf_bulk_delete_queue'.

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 guidance is provided on when to use this tool versus alternatives such as 'bookshelf_bulk_delete_queue' or 'bookshelf_list_queue'. The description lacks context on typical use cases or exclusions.

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