get_session

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

There are no annotations, so the description must disclose behavior itself. It adds the notable side effect 'Auto-logs in if needed' and the GET method signals a read operation; however, it does not describe the response shape or error/not-found 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?

Two short sentences, front-loaded with the core action and endpoint, with the auto-login side effect in the second. There is no filler or repetition.

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 simple one-parameter getter with no output schema, this is largely complete: it states what is returned ('session and its prompt turns') and the auth-related side effect. It does not cover error cases, but the simplicity of the operation makes that a minor gap.

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?

With only one required parameter and 100% schema coverage, the schema already explains that id is a session ID. The endpoint notation conveys that id is a path parameter, but no extra format or lookup guidance is given, so the description adds only marginal semantic value.

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 names a specific action and resource: 'Get one session and its prompt turns' and gives the exact endpoint. This clearly differentiates it from list_sessions (one vs. many) and list_prompts (prompts as a list).

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 intended trigger is evident: call it when a single session ID is known and its prompt turns are needed. It does not explicitly say 'use list_sessions for all sessions,' so it stops short of naming alternatives.

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