session_get

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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond those, noting that recent request history is included when available, which tells the agent the response content is conditional. No contradictions with the annotations exist.

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 a single focused sentence with no wasted words. It front-loads the core operation and appends the conditional history detail efficiently.

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 one-parameter read tool with strong safety annotations, the description is nearly complete: it identifies the resource, the lookup key, and an important output detail. The only minor gap is that the exact structure of the returned session record is not described, but the phrase 'gateway session record' plus the lack of an output schema keeps this acceptable.

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?

The schema describes sessionId as 'Session ID' and covers 100% of parameters, so the baseline is 3. The tool description repeats the lookup-by-session-ID concept but does not add format, source, or validation details 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?

The description states a specific verb ('Get'), a specific resource ('one gateway session record'), and the lookup key ('by session ID'). It also adds a distinguishing detail ('including recent request history when available') that separates it from broader sibling tools like session_list.

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 'by session ID' phrasing makes it clear this is the targeted single-record retrieval counterpart to session_list, giving implied usage context. However, it does not explicitly say when not to use it or name any alternative tool, so the routing guidance is left mostly to inference.

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