session_get

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read, but does not state whether the session must exist or be active, what happens on an unknown or expired session_id, or what the summary contains — and it does not flag any error behavior.

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?

A single short sentence with no filler, which is structurally clean and front-loaded. But the brevity here is under-specification rather than true conciseness — the sentence is too thin to earn its place as the tool's only guidance.

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?

An output schema exists, so return values need not be described. Still, with zero annotation coverage and a completely undocumented parameter, the description should at minimum clarify the session_id source and when this read is appropriate; those gaps make it incomplete for an agent to invoke correctly.

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% for the single parameter, and the description does not compensate: it never explains what a session_id is, where it comes from (e.g., session_start), or its expected format. With one undocumented required parameter, the description adds no meaning beyond the schema's field name.

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 gives a verb ("Get") and a resource ("one session summary"), and "one" weakly distinguishes it from the sibling session_list. However, "summary" is left ambiguous — it is unclear whether this returns full session state, metadata, or a condensed view — so the agent cannot tell precisely what it retrieves.

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?

There is no guidance on when to use this tool versus session_list, session_state_paths, or session_get_policy, nor any prerequisite such as needing an active session. Usage must be inferred entirely from the name.

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