get_session

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

With no annotations, the description carries the full burden. It discloses that the tool returns 'full detail and current status', which implies read-only behavior, but does not specify side effects, error cases, or permissions. This is typical for a get operation but lacks deeper 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?

Two sentences, front-loaded with action, then usage context. Every word earns its place, with no redundancy or unnecessary detail.

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?

The tool is simple (one parameter, no output schema, no annotations). The description sufficiently explains what it retrieves, when to use, and how the session ID is obtained. It does not detail return format, but the phrase 'full detail and current status' covers this adequately for a simple retrieval.

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%: the parameter sessionId is described as 'Session id from create_session or list_sessions' in the schema. The description adds no extra parameter semantics beyond reinforcing the source of the ID, so 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 uses a specific verb ('Retrieve') and clearly defines the resource ('full detail and current status for ONE verification session'). It distinguishes from siblings by emphasizing 'ONE' session versus list_sessions, and references create_session/list_sessions for context.

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?

Explicitly states when to use: after create_session or after finding a sessionId via list_sessions, and the purpose: check progress/outcome. However, it does not explicitly mention when not to use or name alternatives, though the sibling tool names imply this.

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