bookshelf_bulk_delete_author

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

The annotation already declares destructiveHint=true, and the description merely repeats 'DESTRUCTIVE: this deletes data' without adding new behavioral context. It does not describe side effects, irreversibility, required permissions, or impact on related data, providing no value beyond the structured annotation.

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 concise, with two short sentences that state the action and warn about destructiveness. It is well-structured and front-loaded, but the lack of parameter or usage details means it sacrifices substance for brevity.

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 severely incomplete. It does not explain how to specify which authors to delete, what the bulk scope is, or any consequences beyond 'deletes data'. The presence of an output schema does not compensate for the missing input semantics.

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 input schema contains a single 'body' object with no specified properties and additionalProperties: true, making it a free-form payload. The description provides zero information about what the body should contain to identify authors for deletion. With 0% schema description coverage, the tool is unusable without external knowledge.

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 the tool performs a 'bulk delete' on 'author editor', clearly indicating a destructive operation targeting authors. This distinguishes it from sibling tools like bookshelf_delete_author (single) and bookshelf_bulk_update_author. However, the phrase 'author editor' is slightly ambiguous, preventing a perfect score.

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 explicit guidance is given on when to use this tool versus alternatives. The description does not mention that this is for deleting multiple authors at once or how it differs from the single delete_author tool. The destructive warning is a caution, not a usage guideline.

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