bookstack_chapters_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 key behavioral traits: it's destructive (deletes chapter and pages) but reversible (moves to recycle bin where it can be restored). This covers safety and reversibility, though it could add more context like permissions or side effects.

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 and adds crucial behavioral context (recycle bin). Every word earns its place with no redundancy or waste.

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 (destructive operation), no annotations, and no output schema, the description is fairly complete. It covers the action, scope, and reversibility, but could improve by mentioning permissions, error handling, or confirmation prompts for better contextual understanding.

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%, with the parameter 'id' clearly documented in the schema. The description does not add meaning beyond the schema, as it doesn't specify parameter details like format or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 chapter and all its pages') and distinguishes it from siblings like 'bookstack_chapters_update' or 'bookstack_recycle_bin_delete_permanently' by specifying the scope (chapter + pages) and the recycle bin behavior. It uses precise verbs and resources.

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 deletion with a recycle bin option, but does not explicitly state when to use this versus alternatives like 'bookstack_recycle_bin_delete_permanently' for permanent deletion or 'bookstack_chapters_update' for modification. It provides some context but lacks explicit guidance on alternatives or exclusions.

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