read_session

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

Annotations already declare the operation read-only, idempotent, and non-destructive; the description reinforces this by noting the original session is preserved. It adds a small amount of useful context about returning display text, but no additional behavioral details such as formatting, truncation, or side effects.

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?

Two short sentences deliver the core action and a safety guarantee with no filler. The most important information is front-loaded and every sentence earns its place.

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?

The tool has no output schema, and the description gives only a minimal hint of return content (display text). Required parameters and defaults are left to the schema, while the description does not explain how maxChars or maxMessages affect the result or when this tool should be chosen over sibling tools.

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 only 40%, and the description contributes no parameter-level meaning. Parameters like maxChars, maxMessages, and sessionId remain unexplained by both the schema and the description, so the low coverage is not compensated.

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 states a specific action (reads display text) on a specific resource (the selected session) and adds a preservation guarantee. It is clear enough to be distinguished from list_sessions and prepare_handoff, though it does not explicitly name or contrast the 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?

The phrasing implies the tool is used when an agent needs the rendered text of a specific session, but no explicit when-to-use, when-not-to-use, or alternative conditions are provided. It does not explain how this relates to list_sessions or prepare_handoff.

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