View 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 one genuinely useful behavior — that results are ordered/limited to the most recent N thoughts rather than the whole session — which the schema's 'limit' field does not state. It says nothing about permissions, pagination behavior across offsets, or what happens when the session does not 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?

Two short sentences, front-loaded with the purpose and immediately followed by the default-return behavior. No filler.

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?

There is no output schema, so the description must carry more weight, yet it does not describe the shape of a returned thought or session, nor error behavior for missing sessions. For a three-parameter read tool the coverage is adequate but leaves real gaps.

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 100%, so limit, offset and sessionName are all documented in the schema, including the category:name:subcategory format and the SESSION_MAX_RETURN default. The description adds only the 'last N' framing and no further parameter semantics; baseline 3 is correct.

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?

States a clear verb+resource ('View the contents of a thinking session') and adds a scope note about the default return window. It does not, however, distinguish itself from closely related siblings such as search_in_session or get_session_info, so an agent must infer which to pick.

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 when-to-use guidance is given. The description implies reading a whole session, but with search_in_session and get_session_info in the sibling set, the agent gets no signal on when this tool is preferable to those. The 'last N by default' note is a default, not a usage rule.

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