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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds genuinely useful context beyond that by enumerating the visibility scope (public campaign pages, ref-less public pages, own pages, GM-side pages when refId scopes to one record) and the Admin Mode bypass. Pagination/row-limit behavior is the only notable omission.

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?

Purpose and the recap recipe are front-loaded, and the default-vs-full behavior follows predictably. The closing visibility sentence is a long four-clause enumeration that is dense but each clause carries distinct authorization meaning, so little is wasted.

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 an output schema present, the description need not explain return shapes, and it correctly avoids doing so while still covering the two things structured fields can't express: the authorization scoping rules and how to combine filters for the common recap lookup. Nothing an agent needs to call this correctly is missing.

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 parameter documentation is already strong and the baseline is 3. The description goes beyond it by showing how refType, refId, and documentType compose in one call and by spelling out the observable effect of detail:'full' (page body markdown inline) rather than just restating the enum.

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?

States a specific verb+resource ('List play pages') and immediately narrows scope to what it can be filtered by and what it returns. An agent can distinguish it from the many page-list siblings (play_list_user_pages, imagine_list_adventure_pages) by domain, but the description never names or contrasts those alternatives explicitly.

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?

Gives a concrete recipe for a primary use case ('To find session recaps, pass refType: session, refId, documentType: player-recap'), which tells the agent exactly how to invoke it for that scenario, plus the default vs. detail:'full' choice. It stops short of stating when *not* to use it or naming a sibling as the alternative.

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