Displays a task session's goal, entries, plan, position, and recorded results; omit session_id to list recent sessions. Use it to check progress or find sessions.
Show a session's goal, entries, plan, position, and recorded results. Without a session_id, list recent sessions.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | No |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a safe read of session state and discloses the list-vs-detail mode switch, but says nothing about permissions, result volume, ordering of recent sessions, or how much history is returned.
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 sentences, no filler, with the primary behavior front-loaded and the alternative mode as a second short clause.
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?
With one optional parameter and no output schema, the description adequately covers return values by naming the facets returned. Only ordering/pagination details for the recent-sessions mode are absent, a minor gap for this complexity level.
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% and the parameter has a bare default of empty string, but the description compensates by explaining that an omitted session_id switches the tool into a recent-sessions listing mode. That is the exact semantic an agent needs beyond the schema.
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?
States a specific verb (show) and resource (a session's status), and enumerates the returned facets (goal, entries, plan, position, results), which separates it from action-oriented siblings like start_session and end_session. It does not explicitly distinguish itself from current_step or get_process_step, which also read session state.
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 gives clear mode guidance for its single parameter ('Without a session_id, list recent sessions'), which is genuinely useful. However, it offers no guidance on when to prefer this aggregation tool over narrower siblings such as current_step or get_matrix.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.