Get session detail

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

No annotations exist; the description only lists output fields. It does not disclose behavioral traits such as read-only nature, error handling for invalid sessionId, authentication requirements, or rate limits. The description carries the full burden here but fails to provide meaningful behavioral context.

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 concise sentence that front-loads the action ('Get one session') and lists outputs. 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 retrieval tool with one parameter and no output schema, the description reasonably covers what the tool returns. However, it omits error scenarios, response format details, and any read-only assurance. Slightly incomplete but adequate.

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 coverage is 100%, with parameter sessionId described as 'Session ID (GUID) from list_sessions'. The description adds no additional meaning beyond the schema; it lists what the tool returns but does not elaborate on the parameter's usage or format. Baseline 3 is appropriate.

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 explicitly states 'Get one session' and lists returned fields (result, state, progress percentage, start/end time, per-object results). It clearly differentiates from sibling tools like list_sessions (which lists multiple) and stop_session (which stops).

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?

No explicit guidance on when to use or not use this tool versus alternatives like list_sessions or get_session_logs. Usage is implied (retrieve details of a single session) but no exclusions or context provided.

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