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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds meaningful workflow context (read-after-conflict, read-before-editing-old-revision) and clarifies that checkpoints are restorable states. However, it never mentions the required 64-hex token as an auth requirement or what happens on an invalid/expired session.

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?

Three short sentences, zero filler, with the returned-field list and the checkpoint flag guidance front-loaded. Every sentence carries actionable information.

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 no output schema, the description compensates by naming the fields returned (preset, revision, expiry, checkpoint summaries). The remaining gap is auth semantics for the required token parameter and error/expiry behavior on the session itself.

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 description coverage is 0%, so the description must carry the load. It explains the checkpoints flag well ('retrieve restorable states'), but token and sessionId are left to their names/patterns with no guidance on where the token comes from or what an invalid one does.

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 and resource ('Read the shared preset, current revision, expiry, and checkpoint summaries') and enumerates what is returned. It is clearly distinguishable from edit_session, checkpoint_session, and restore_session by name, though it never explicitly names a sibling as an alternative.

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 concrete conditional guidance: 'Include checkpoints=true to retrieve restorable states' and 'Always read after a conflict and before editing an old revision.' This is real when-to-use advice, but it offers no exclusions or pointers to wait_for_changes / describe_nodes for other state-inspection needs.

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