bookshelf_bulk_delete_blocklist

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

The description says 'DESTRUCTIVE: this deletes data,' but this entirely duplicates the annotation destructiveHint=true. No additional behavioral context is provided, such as irreversibility, required permissions, or impact on related resources. The description adds no value beyond the 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 awkwardly phrased: 'Bulk delete blocklist bulk' repeats 'bulk' and is grammatically clunky. The second sentence only repeats the annotation. It is concise, but the wording could be much clearer and each sentence does not earn its place effectively.

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?

With a single parameter that has no description, and no details about the body content, the tool is operationally unclear. While an output schema exists and annotations cover destructiveness, the missing input semantics leave a significant gap for a destructive bulk operation.

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?

The body parameter is completely undefined. The schema shows an empty object with additionalProperties true, and the description gives no hint about what should be sent (e.g., list of blocklist IDs). With schema description coverage at 0% and no compensation from the description, the agent cannot know how to construct the request.

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 clearly states the action: 'Bulk delete blocklist bulk.' The verb 'bulk delete' and resource 'blocklist' make the purpose understandable, and the bulk aspect distinguishes it from the singular sibling bookshelf_delete_blocklist. However, the phrase 'blocklist bulk' is awkward and could be clearer, so it doesn't earn a 5.

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 guidance on when to use this bulk delete tool versus the singular delete_blocklist tool. No mention of prerequisites, typical use cases, or alternatives. The description is purely a statement of action without context for selection.

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