bookstack_books_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 explains that deletion moves items to a recycle bin rather than permanent removal, which is crucial behavioral context not evident from the name alone. However, it doesn't mention permission requirements, rate limits, or error conditions.

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 communicates the core action and important behavioral detail without any wasted words. It's front-loaded with the primary purpose and follows with clarifying context.

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 destructive operation with no annotations and no output schema, the description provides essential context about the recycle bin behavior. However, it doesn't mention what happens to associated content (chapters, pages) or whether deletion requires specific permissions. Given the single parameter and clear schema, it's mostly complete but could benefit from more behavioral detail.

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 single parameter 'id' clearly documented as 'Book ID to delete'. The description doesn't add any additional parameter semantics beyond what's in the schema, but since the schema is complete, 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 action ('Delete a book') and specifies the resource ('book'), distinguishing it from sibling tools like 'bookstack_books_update' or 'bookstack_books_list'. It also adds important context about the deletion behavior ('moves to recycle bin where it can be restored'), which helps differentiate it from permanent deletion tools like 'bookstack_recycle_bin_delete_permanently'.

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 deleting books via ID, but doesn't explicitly state when to use this tool versus alternatives like 'bookstack_recycle_bin_delete_permanently' or 'bookstack_recycle_bin_restore'. It provides basic context (deletion with recovery option) but lacks explicit guidance on prerequisites or exclusions.

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