Read session transcript

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does well by revealing that the transcript includes work from phone and claude.ai sessions and explicitly excludes subagent sidechains and tool plumbing. This goes beyond a generic 'reads transcript' statement, though it does not mention response format or other edge behaviors.

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 two sentences with no filler. The main action is stated first, and the second sentence adds valuable exclusions/inclusions that would otherwise be unknown. Every clause 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?

For a relatively simple read operation with a small, fully described schema, the description covers the essential context: what is returned, what additional sources are included, and what is omitted. It could be slightly more explicit about return shape or the fact that it is non-mutating, but the name and verb make this largely evident.

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?

The input schema already provides descriptions for all three parameters, including defaults and ranges, so schema coverage is 100%. The description adds no additional parameter-level semantics beyond calling the resource a 'session,' which aligns with the schema. Baseline of 3 is appropriate because the schema carries the parameter documentation burden.

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 clear verb ('Read') and resource ('recent conversation turns from a session'). It also adds distinguishing scope, noting that phone-driven and claude.ai-driven work are included, and that subagent sidechains and tool plumbing are omitted. This makes the tool's purpose unambiguous even among siblings like list_sessions and get_reply.

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 implies its use case: reading recent conversation history from a session. However, it does not explicitly contrast it with sibling tools or state conditions like 'use get_reply when you need a single reply' or 'use list_sessions to enumerate sessions.' Usage context is clear but not explicitly differentiated.

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