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

Annotations already cover readOnly, idempotent, non-destructive, openWorld. The description usefully adds content-boundary guarantees (no raw keys, no invitation credentials, no hidden opponent state), which is real value beyond annotations. However it says nothing about size limits of the 'bounded' snapshot, pagination, or revision semantics, so behavioral disclosure is partial.

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 compact sentences, front-loaded with the read action, followed by the leakage boundaries and the injection warning. The prompt-injection warning is generic boilerplate but defensible given the sibling set includes chat and participant content, so little waste overall.

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?

There is no output schema, so the description carries the burden of explaining what a 'snapshot and revision' actually returns, and it never does. It compensates well on the safety side but leaves an agent guessing about the response structure for a one-parameter read tool.

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 'session' parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no meaning about what the session string identifies or how an invalid or closed session is handled.

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 a bounded participant-visible snapshot and revision.' An agent can tell this is a read of session state rather than a listing (session_list) or a blocking wait (session_wait), though 'snapshot' and 'revision' are never unpacked, leaving the exact payload shape fuzzy.

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?

No when-to-use guidance and no named alternatives, despite tight siblings like session_wait, session_list, and participant_preflight that a caller could easily confuse with this one. The only directive is a safety rule about untrusted content, not usage selection.

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