bookshelf_bulk_delete_indexer

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

The annotations already declare destructiveHint=true and readOnlyHint=false. The description's 'DESTRUCTIVE: this deletes data' adds no additional behavioral context beyond what the annotation already signals. It does not disclose irreversibility, side effects, or what specific data will be deleted.

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 short sentences, so it is concise in length. However, the first sentence 'Bulk delete indexer bulk' is redundant and could be reduced; the second sentence is repetitive of the annotation. The structure is not front-loaded with key information beyond the name and destructive hint.

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 bulk operation, the description is incomplete. It does not explain the payload structure ('body' object), what data is affected, or how the operation behaves (e.g., partial failures, confirmation). While an output schema exists and annotations signal destructive intent, the lack of parameter guidance and usage context makes this insufficient.

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 schema defines a single 'body' object parameter with additionalProperties true, but provides no property descriptions (schema coverage 0%). The tool description does not explain what the body should contain (e.g., IDs, filter criteria) or how to structure a bulk delete request. This is a significant gap since the description is the only source of parameter meaning.

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 'Bulk delete indexer bulk' identifies the tool as performing a bulk delete operation on indexers, but the phrasing is awkward and redundant. It is clear enough that this is a delete operation for indexers in bulk, distinguishing it from the single 'bookshelf_delete_indexer' sibling, but does not clearly state the scope (e.g., multiple IDs, filters, or all 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?

There is no guidance on when to use this bulk delete tool versus alternatives like the single 'bookshelf_delete_indexer'. The description only warns 'DESTRUCTIVE: this deletes data,' which is a safety warning, not a usage recommendation. No exclusions or conditions are provided.

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