get_session

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

With no annotations, the description itself must indicate side effects. The verb 'Retrieve' makes it clear this is a read-only operation, and the phrase 'with its events and checkpoint' discloses the returned data. However, it does not address failure behavior for missing/invalid IDs or any permission requirements, though these are minor for a simple getter.

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 a single sentence with no filler. The core operation is front-loaded, and the qualifiers 'with its events and checkpoint' are appended 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?

This is a simple one-parameter getter with no output schema, and the description provides the essential return content (events and checkpoint). It could be more explicit about what happens when the session ID is not found, but for a straightforward retrieval tool the description is adequately complete.

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 a 100% description for the sole parameter session_id ('The session ID'), so the description's job is minimal. The description does not add any additional format, example, or source for the session ID beyond what 'by ID' implies, so it earns the baseline for high schema coverage.

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 uses the specific verb 'Retrieve' and identifies the resource 'a session by ID', specifying the return content 'with its events and checkpoint'. This clearly separates it from sibling tools like get_active_session, which would not require an explicit session_id.

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 usage when the caller has a specific session ID and needs its events/checkpoint, but it does not explicitly name alternatives or say when not to use it. No exclusion criteria or comparison with get_active_session/list_sessions is provided, leaving the selection logic implicit.

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