get_session

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

No annotations are provided, so the description carries the full burden. It describes what the tool returns ('full message flow'), but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or whether it's a read-only operation (though 'retrieve' implies reading). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 that are front-loaded and efficient. The first sentence states the core purpose, and the second adds valuable detail about the content retrieved. There is no wasted language, and every sentence earns its place by enhancing clarity.

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 the tool has an output schema (which likely describes the return structure), the description doesn't need to explain return values. However, with no annotations, 3 parameters (one required), and 0% schema description coverage, the description is incomplete—it lacks parameter details and behavioral context. It's minimally adequate but has clear gaps for a retrieval tool.

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 0%, so the schema provides no descriptions for parameters. The description adds no information about parameters beyond what the schema names imply (e.g., session_id, limit, offset). It doesn't explain what a session_id is, how limit/offset affect pagination, or any constraints. With low coverage, the description fails to compensate, resulting in a baseline score.

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 verb 'retrieve' and the resource 'conversation from a specific session', and specifies the content includes 'user messages, assistant responses, and tool usage'. It distinguishes from siblings like list_sessions or search_sessions by focusing on retrieving a specific session's content rather than listing or searching. However, it doesn't explicitly contrast with siblings like refresh_sessions, so it's not a perfect 5.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use get_session over list_sessions or search_sessions, nor does it specify prerequisites or exclusions. The context is implied by the action of retrieving a specific session, but no explicit usage rules are given.

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