bookshelf_delete_blocklist

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

The description repeats the destructiveHint annotation by saying 'DESTRUCTIVE: this deletes data' but adds no additional context such as what gets destroyed, irreversibility, or permission requirements. With annotations already covering the destructive nature, the description provides no extra value.

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 extremely short and front-loaded, consisting of two sentences. The second sentence is somewhat redundant with the annotation, but the overall length is appropriate for such a simple tool, with no extraneous content.

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?

Given the simple tool with one parameter and existing annotations, the description is thin. It does not clarify the exact resource being deleted or the meaning of the 'id' parameter, and offers no usage guidance. The presence of an output schema reduces the need to describe return values, but the description still feels incomplete.

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% and the description does not explain the 'id' parameter. While the parameter is simple and self-explanatory as an identifier, the description does not clarify whether it refers to a blocklist entry or the blocklist itself, which is important for correct usage.

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 uses the specific verb 'Delete' with the resource 'blocklist', clearly indicating a delete operation. It is distinguished from siblings like bookshelf_list_blocklist and bookshelf_bulk_delete_blocklist by being a singular delete, though it does not specify whether it deletes an entry or the entire blocklist.

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_blocklist or bookshelf_list_blocklist. The description only states the action without context or exclusions.

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