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

The description adds substantial context beyond the destructiveHint annotation: immediate permanent deletion for unpublished items, draft-only removal for published items, live Riddle dependency until purge, restore via discard changes, no trash/restore, and access requirements. It is fully consistent with annotations.

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 dense but front-loaded and every sentence carries operational meaning. It communicates destructive consequences, related siblings, access needs, and rejection conditions without filler.

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 mutation tool with no output schema and fully covered parameters, the description provides the critical missing behavioral context: permanence, draft semantics, dependency on publish, restore path, and access requirements.

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 both parameters are already well documented in the schema. The description reinforces that only one item is deleted but does not add syntax or format details beyond the structured parameter definitions.

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 states a specific verb and resource: deletes exactly one question bank item and touches nothing else. It clearly distinguishes this from sibling operations like question_bank_delete, question_bank_publish, and question_bank_discard_changes.

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?

It explains the key conditional behavior for never-published versus published items and explicitly names question_bank_publish and question_bank_discard_changes as the operations that affect the item afterward. It also states access requirements and the public-template rejection condition.

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