Load a shared session

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value on top by disclosing default behavior ('tail' is default), the payload shape, and that 'full' is paged via offset. It does not state sharing/permission prerequisites or any size limits for retrieving a shared session, which would have pushed this higher.

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?

Very compact: one sentence naming the payload followed by a terse mode legend, with the default mode stated up front. It is dense but every clause carries information; a slightly cleaner breakdown of mode-to-parameter pairing would earn a 5.

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 does the necessary work of naming returned content and explaining paging, which is enough for an agent to call it correctly. Missing pieces are minor: where the id comes from is only in the schema, and there is no mention of permission or sharing requirements for open-world session access.

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%, so baseline is 3, but the description adds semantic meaning beyond the schema: it clarifies the interplay of mode with offset ('full' = full transcript, paged with offset) rather than merely restating the enum values. The 'tail' integer parameter's interaction with mode is only implied, not spelled out in the description.

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 ('Load a shared session') and enumerates the payload an agent gets back: summary, decisions, next steps, files and conversation. It does not explicitly differentiate itself from the similarly-named sibling get_session_diff or point to list_sessions/search_sessions for id discovery, so sibling routing is left to inference.

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?

Explains the three modes and their trade-offs clearly — 'tail' (default) for summary plus recent messages, 'summary' for summary only, 'full' for the complete transcript with offset paging. What is missing is guidance on when to prefer a sibling such as get_session_diff or when to fall back to search_sessions instead of loading.

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