bookshelf_delete_indexer

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows the operation is destructive. The description's 'DESTRUCTIVE: this deletes data' adds no new behavioral traits beyond what the annotation and tool name already convey; it fails to disclose specifics like permanence, cascading effects, or required authorization.

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 (two sentences) and front-loads the verb. The second sentence is somewhat redundant with the destructive annotation, but overall it is not padded and conveys the core action efficiently.

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 with one required parameter and an output schema, the description is minimal but not wholly inadequate. However, it omits important context such as whether the deletion is permanent, any dependencies, or what the response indicates, making it only partially complete for an agent.

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 a single 'id' parameter with no description, and schema description coverage is 0%. The description does not explain what 'id' refers to (presumably the indexer ID), leaving the agent to infer from the tool name and context.

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 clearly states the action ('Delete') and the resource ('indexer'), which distinguishes it from tools targeting other resources. However, it does not explicitly differentiate between single delete and bulk delete, though the singular noun and the required 'id' parameter imply a single-item operation.

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 about when to use this tool versus alternatives such as 'bookshelf_bulk_delete_indexer' or 'bookshelf_update_indexer'. The description only states the action and a warning, leaving the agent without context on prerequisites or selection criteria.

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