bookstack_images_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively discloses that the action is permanent ('cannot be undone'), which is a critical behavioral trait for a destructive operation. However, it does not mention other aspects like required permissions, error handling, or rate limits, leaving some gaps.

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 a single, efficient sentence that front-loads the key information ('Delete an image permanently from the gallery') and adds a crucial warning ('this action cannot be undone') without any wasted words. Every part of the sentence serves a clear purpose.

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 tool's complexity (a destructive operation with one parameter), no annotations, and no output schema, the description is reasonably complete. It covers the permanent nature of the deletion, which is essential, but could be more complete by addressing permissions or error scenarios, though it meets most needs for this context.

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 schema description coverage is 100%, with the parameter 'id' clearly documented as 'Image ID to delete'. The description does not add any additional meaning beyond what the schema provides, such as format details or examples. With high schema coverage, the baseline score of 3 is appropriate.

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 specific action ('Delete an image permanently from the gallery') and resource ('image'), distinguishing it from siblings like bookstack_images_create, bookstack_images_list, bookstack_images_read, and bookstack_images_update by focusing on deletion rather than creation, listing, reading, or updating.

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?

The description implies usage for permanent deletion of images, but does not explicitly state when to use this tool versus alternatives like bookstack_recycle_bin_delete_permanently or bookstack_attachments_delete, nor does it provide exclusions or prerequisites. The context is clear but lacks explicit guidance on alternatives.

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