bookstack_roles_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the option to migrate users, which adds some context beyond a basic delete. However, it fails to cover critical aspects like permissions required, whether deletion is permanent or reversible, error conditions (e.g., if role doesn't exist), or side effects. For a destructive operation with zero annotation coverage, this is inadequate.

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 role') and adds necessary detail ('with option to migrate users to another role'). There is no wasted verbiage, making it highly concise and well-structured.

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 complexity of a deletion tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., permanence, permissions), error handling, and what the tool returns. While concise, it doesn't provide enough context for safe and effective use by an AI 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?

Schema description coverage is 100%, so the schema already documents both parameters ('id' and 'migrate_ownership_id') clearly. The description adds minimal value by implying the optional migration feature but doesn't provide additional semantics (e.g., what happens if migration is omitted). Baseline 3 is appropriate when the 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 action ('Delete a role') and specifies the resource ('role'), making the purpose unambiguous. It distinguishes from sibling tools like 'bookstack_roles_list' or 'bookstack_roles_update' by focusing on deletion. However, it doesn't explicitly differentiate from 'bookstack_roles_delete' (itself) or other deletion tools in terms of scope, so it's not a perfect 5.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., role existence), exclusions (e.g., cannot delete default roles), or compare to other deletion tools (e.g., 'bookstack_users_delete'). Usage is implied by the action but lacks explicit context.

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