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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds meaningful context beyond that: the explicit auth parameter semantics, the privacy boundary limiting reads to one's own role, and the fact that AI replies include token counts. It omits anything about log size, pagination, or truncation behavior for potentially large sessions.

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?

A single dense paragraph that front-loads what the tool returns, then parameters, then prerequisites, then access limits. Every clause carries information (contents, params, source of session_id, privacy, auth), with no filler or repetition.

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 carries the burden of explaining return content and does so by enumerating the record types. Auth and privacy constraints are covered. The main remaining gap is volume/pagination behavior for a full session log, which an agent might need to handle large sessions.

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 0% and both parameters are undocumented in the schema, so the description must compensate. It states both are required, explains slug as the explicit auth handle, and tells the agent where a valid session_id comes from — enough to invoke correctly despite the bare schema.

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 (retrieve a single session's full chronological log) and enumerates exactly what the stream contains: user messages, AI replies with tokens, tracking events, action calls, screen pushes. It distinguishes itself from the sibling list_sessions by describing a per-session detail dump rather than a listing.

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 prerequisite: obtain a valid session_id from list_sessions or open_canvas before calling. It also states the access condition (only your own role's records; valid Key required, anonymous not enabled). It does not explicitly say when NOT to use this tool versus list_sessions for bulk inspection, so it falls short of a full when/when-not routing statement.

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