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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description adds genuinely new behavior beyond them — result ordering (newest first) and the exact fields returned — which matters because there is no output schema. It still omits whether the listing is limited, paginated, or empty-campaign behavior.

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 first sentence is front-loaded and informative, but the second sentence, 'Returns: The sessions.', restates the same content and earns no place. Two short sentences with one redundant — adequate but not tight.

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 one-parameter read-only list tool with no output schema, enumerating the returned fields partially compensates. However, given no output schema, the description should also settle scoping (per-campaign), volume/pagination expectations, and whether ordering is stable — none of which appear.

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 documented as slug-or-id in the schema, so the baseline is 3. The description adds nothing about the parameter and, notably, never states that results are scoped to that campaign, which is the one semantic an agent might want confirmed.

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 conveys what comes back (title, number, note count, recap, newest first) but never uses a clear verb+resource framing such as 'list all sessions in a campaign' — it says 'Every play date,' which requires the reader to map 'play date' to 'session'. It also gives no signal distinguishing it from get_session or the many other list_* 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?

There is no when-to-use guidance at all: no mention of reaching for this instead of get_session for a single session, and no stated prerequisite (e.g., that the campaign must exist or that the caller must be a participant). The ordering note ('newest first') is descriptive, not usage guidance.

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