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

Annotations already declare destructive=true, idempotent=false, openWorld=false and readOnly=false, so the risk profile is known. The description adds real value on top: a permission requirement (GM only), a recovery path via `reopen_campaign`, the confirmation ritual, and a stated return value — none of which the annotations convey.

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?

Four short sentences, front-loaded with the action and followed by confirmation, reversibility, authorization, and return value in that order. The opening idiom is atmospheric but costs a beat of clarity, and the "Returns: The memorial state" fragment is terse to the point of being cryptic.

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, non-idempotent, two-parameter mutation with no output schema, the description covers the essentials: what it does, who may do it, how confirmation works, what reverses it, and roughly what comes back. The one soft spot is that "the memorial state" is never explained, though the `get_memorial` sibling offers an implicit path to it.

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 coverage is 100%, so both parameters are already documented; the description still reinforces that `confirm` must be the campaign's own name typed back, which clarifies the validation intent beyond the terse schema line. Slight duplication keeps it just under the top band rather than adding format or matching rules.

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?

"Close the book" plus the title and the explicit tension with the sibling `reopen_campaign` makes it clear this terminates/finalizes a campaign rather than reading or editing it. The core verb is metaphorical rather than literal, but the surrounding text removes ambiguity about which resource is affected.

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 names the reversal path (`reopen_campaign`), states the GM-only audience, and explains the typed-name confirmation protocol. What's missing is a note on when completing is appropriate versus simply leaving a campaign inactive, but the exclusions and preconditions given are strong.

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