bookshelf_delete_customformat

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

The description simply restates the destructiveHint annotation ('DESTRUCTIVE: this deletes data.') without adding additional behavioral context such as irreversibility, cascading effects, or permission requirements. With annotations already covering destructiveness, the description contributes no new transparency.

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 very brief, consisting of two short sentences that make the destructive nature clear. Each sentence earns its place, though the second sentence repeats the annotation. It is concise without being verbose, but could be considered slightly underspecified.

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?

The tool is a simple delete operation with one parameter and an output schema, so a short description might suffice. However, the description omits that the deletion is by ID, potential side effects, and any prerequisites. It is minimally adequate but lacks completeness for an agent to fully understand the 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 input schema has one required 'id' parameter with 0% schema description coverage, but the description does not explicitly state that the customformat is deleted by ID. The meaning of 'id' is inferable from the tool name and schema, but the description adds no semantic detail beyond the schema.

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 explicitly states 'Delete customformat' with a specific verb and resource, clearly distinguishing it from sibling tools like bookshelf_delete_customfilter and bookshelf_delete_author. The resource name matches the tool name exactly, leaving no ambiguity about the target.

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 for when to use this tool versus alternatives. It is implied that this tool is for deleting a customformat, but there are no contextual cues, prerequisites, or exclusions. The destructive warning adds caution but not usage context.

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