get_session

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

With no annotations, the description carries full burden. 'Fetch' implies a read operation, and it adds context about optional markdown handoff and resume prompt. However, it does not disclose permissions, error behavior, or whether the handoff is freshly generated or stored.

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?

Single sentence, front-loaded, no wasted words.

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 fetch tool with no output schema, the description covers the essential action and optional behavior. It doesn't explain what the markdown handoff or resume prompt are, but the core use is clear. Slightly more detail on those concepts would improve it.

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 description must compensate. It provides some mapping: 'by ID' for session_id and 'optional markdown handoff and resume prompt' for include_handoff/target_assistant, but it does not explicitly describe each parameter's value format or constraints.

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 'Fetch' with resource 'one session by ID', clearly distinguishing it from sibling tools like list_sessions and get_latest_session. It also notes optional markdown handoff and resume prompt, which defines its unique scope.

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 conveys clear context for when to use (fetching a specific session by ID) but does not explicitly mention alternatives or exclusions. It implies 'use this when you need exactly one session by ID' without naming sibling tools.

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