get_claude_session

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

With no annotations, the description carries full burden and effectively discloses that the tool returns a transcript with ordered messages and timestamps, excludes internal thinking blocks by default, and that these can be included via the include_thinking parameter. No destructive behavior is implied, and no contradictions exist.

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?

The description is concise, with a clear opening sentence stating the purpose, followed by a brief summary of return content, and an organized list of parameters. Every sentence adds value without redundancy.

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?

Given an output schema exists, the description adequately covers expected return content (messages, timestamps, tool names) and optional thinking. It lacks mention of error handling or edge cases, but overall provides sufficient context for an agent to invoke the tool correctly.

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?

Since the input schema has 0% description coverage, the description fully compensates by explaining that session_id is a UUID from list_claude_sessions, project_slug identifies the project, and include_thinking controls inclusion of thinking blocks, with default false. Each parameter's meaning and source are clarified.

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 clearly states the tool retrieves the full conversation transcript from a Claude Code session, specifying it returns user and assistant messages with timestamps and tool call names, distinguishing it from sibling tools like get_claude_session_stats which provides statistics.

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 description explains what the tool does and returns, but does not explicitly state when to use this tool versus alternatives like search_claude_sessions or list_claude_sessions. No exclusions or context for when not to use are provided.

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