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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses important behavioral details: caller must be a campaign member, visibility follows play page rules, campaigns without tagged sessions are omitted, and the empty result shape is `{ campaigns: [] }`. This is exactly the kind of access-control and filtering context annotations do not capture.

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 purposeful, covering purpose, data shape, access rules, empty behavior, and the manual alternative in roughly four sentences. It is front-loaded with the core action and grouping, though the middle data-shape sentence is somewhat detailed given that an output schema already exists.

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 read-only fetch tool with one well-documented parameter and an output schema, the description is complete: it explains what is fetched, how results are grouped, who can access what, when campaigns are omitted, and what the empty response looks like. Nothing an agent needs to invoke it 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?

The single parameter `id` is already fully documented in the schema as the Mongo `_id` of the adventure, so the schema description coverage is 100%. The description adds no new parameter-level detail, but it does reference 'this adventure' contextually; baseline 3 is appropriate when the schema carries the parameter meaning.

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 first sentence states a specific verb ('Fetch'), a precise resource ('play-session recaps written while running this adventure'), and the grouping behavior ('grouped by linked play campaign'). It also explicitly distinguishes itself from the manual walk of play_list_campaign_sessions + play_list_pages, so an agent can separate it from siblings.

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 description gives clear context: it is the recaps-only path for private adventures, requires membership in a linked campaign, and is positioned as the replacement for a manual multi-tool walk. It does not explicitly state when-not to use it versus sibling listing tools, but the alternative is named and the access conditions make usage clear.

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