get-session

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

No annotations are provided, so the description carries the full burden. It states a safe read operation ('Get a single session'), which is consistent with the tool's behavior. However, it lacks details on potential errors, permissions, or edge cases. The expected return is mentioned but not the structure of the session object.

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 concise with 4 sentences plus an example. It is front-loaded with the purpose. The example is useful but could be more precise. No unnecessary information.

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?

No output schema is provided, so the description should elaborate on the return structure. It mentions a 'session object and, optionally, its annotations', but without further detail. Given the tool's simplicity, this is minimally adequate but not comprehensive.

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 0%, so the description must explain parameters. It does mention that session_identifier can be a GlobalID or user-provided session_id, and that include_annotations is optional. However, it does not specify the format of the identifiers or what annotations include, leaving room for ambiguity.

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 clearly states it retrieves a single session by an identifier, distinguishing it from list-sessions which returns multiple sessions. The verb 'get' and phrase 'single session' are specific. However, it does not explicitly differentiate between using GlobalID vs user-provided session_id in terms of syntax, which could be clearer.

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 this tool versus alternatives like list-sessions. The example 'Show me session "chat-123"' implies usage when an identifier is known, but there is no discussion of prerequisites or scenarios where other tools are more appropriate.

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