bookstack_pages_delete

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

With no annotations provided, the description carries the full burden. It discloses that deletion is not permanent (moves to recycle bin) and implies restorability, which are key behavioral traits. However, it lacks details on permissions, error conditions, or what happens if the ID is invalid, leaving gaps for a mutation tool.

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 core action ('Delete a page') and adds critical context ('moves to recycle bin where it can be restored') without any wasted words. Every part earns its place.

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 tool with no annotations and no output schema, the description is minimal but covers the essential behavior (soft deletion). It lacks details on permissions, response format, or error handling, which are important for safe invocation. Given the complexity, it's adequate but has clear gaps.

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 100%, so the schema already documents the 'id' parameter fully. The description adds no additional parameter semantics, but with only one parameter and high schema coverage, the baseline is elevated. It implicitly confirms the parameter's purpose by referencing 'Page ID to delete' in 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 specific action ('Delete a page') and resource ('page'), distinguishing it from siblings like 'bookstack_pages_update' or 'bookstack_recycle_bin_delete_permanently'. It adds nuance by specifying that deletion moves the page to a recycle bin, which is not obvious from the tool name alone.

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 implicitly provides usage context by mentioning the recycle bin, suggesting this tool is for soft deletion rather than permanent removal. However, it does not explicitly state when to use this versus alternatives like 'bookstack_recycle_bin_delete_permanently' or provide prerequisites (e.g., required permissions).

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