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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds the useful constraint that this concerns completed campaigns and lists included content, but it does not say what happens if the campaign is unfinished or has no Lorekeeper write-up (error vs. partial result).

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 definition is brief and front-loads the resource, but 'Returns: The memorial.' is a pure tautology that restates the tool name and earns nothing. The content list is dense with in-world terms that could be plainer.

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?

With one required parameter, no output schema, and full annotation coverage, the description needs mainly to characterize the return payload. It gestures at the contents (numbers, party, album, write-up) but vaguely, and leaves edge-case behavior (no memorial yet, campaign not completed) unexplained.

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% and the single campaign parameter is fully documented as accepting a slug or id. The description adds nothing about the identifier, so baseline 3 applies.

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 identifies the resource (a completed campaign's memorial) and enumerates its contents, which hints at the distinction from get_campaign. However, it is a noun fragment rather than a verb+resource statement, and phrases like 'the numbers' and 'the album' are flavorful but imprecise about what is actually returned. An agent can mostly infer the purpose but not crisply.

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 only usage signal is implicit in 'a completed campaign's memorial', suggesting it applies after completion. There is no explicit when-to-use, no when-not, and no reference to the obvious alternative get_campaign or set_memorial_public.

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