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

With no annotations present, the description carries the full burden and delivers richly: it discloses irreversibility (no undo, no copy), edge-case behavior (pending deletes come back, added items are left alone), scope limits (title/notes are metadata and never change), and the public-template rejection.

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?

A dense single paragraph where every sentence earns its place: core action first, then irreversibility, edge cases, scope, alternatives, and rejection. Front-loaded and information-packed, but could be slightly better structured (e.g., bullets) for scannability.

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 an irreversible destructive tool with no annotations and no output schema, the description covers operational semantics thoroughly: what happens, edge cases, scope, preconditions, and alternatives. The only minor gaps are an explicit definition of questionBankId and the success/return behavior.

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 single schema parameter (questionBankId, integer) has no property description, so schema coverage is effectively zero and the description must compensate. It does by tying the parameter to the draft-reset behavior and adding the constraint that public template ids are rejected, though it never formally defines questionBankId itself.

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 opens with a specific verb and resource — throws away every unpublished change to a question bank's items, resetting them to last published content. It also differentiates from siblings by explicitly stating what it is not ('not restore the bank as it was published') and naming the preferred alternative, question_bank_manage(action: 'publish').

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?

Provides explicit when-to-use guidance: read both sides first via question_bank_get_items (draft and published:true), and prefer question_bank_manage(action: 'publish') when the draft should survive. Also states an exclusion: rejected for a public template id.

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