bookshelf_delete_author

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

The DESTRUCTIVE statement merely restates the destructiveHint annotation and adds no new behavioral context, such as whether associated files or books are removed or whether deletion is reversible. With annotations already covering the destructive trait, this description adds little beyond structured data.

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?

Three short sentences with the action front-loaded. However, the query-params line duplicates schema information and uses mismatched casing, and the DESTRUCTIVE line repeats the annotation, so it is concise but not perfectly efficient.

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 simple delete operation, the annotations and output schema cover safety and return expectations, and the destructive warning is present. However, the lack of parameter semantics and alternative guidance leaves the agent to infer the effects of the two boolean options, making it minimally viable rather than complete.

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 description lists deleteFiles and addImportListExclusion but does not explain their effects, and it omits the required id. It also uses camelCase names that do not match the schema's snake_case delete_files and add_import_list_exclusion. With 0% schema description coverage, this fails to compensate for missing parameter meanings.

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 opens with 'Delete author,' a specific verb+resource that unambiguously identifies the operation and distinguishes it from sibling get/update/create/bulk-delete tools. The destructive warning reinforces the intended action.

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_update_author or bookshelf_bulk_delete_author. There are no stated prerequisites, exclusions, or preferred contexts.

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