get-current-session

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

With no annotations, the description carries the full burden. 'Retrieve' suggests read-only behavior, and it discloses the side effect of opening the Research Workspace widget. However, it does not explicitly state that it is safe/non-mutating or describe any potential side effects beyond the widget, leaving some ambiguity.

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 two sentences, with no wasted words. The first sentence states the core functionality and enumerates contents; the second sentence adds a relevant behavioral note about opening the widget. It is concise and well-structured.

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?

Given no output schema, the description provides a good sense of what is returned (topic, papers, reviews, etc.). It also mentions the widget opening, which is useful context. However, it does not specify the structure of the response or behavior when no session exists, leaving minor 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?

The tool has 0 parameters, and the schema reflects this with no properties. Per guidelines, a parameterless tool earns a baseline of 4. The description adds no parameter-specific semantics but is not required to, as there are none.

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 the tool retrieves the entire persistent research session, with a specific verb ('Retrieve') and resource ('research session'). It lists the contents (topic, papers, reviews, gaps, notes, saved papers), distinguishing it from siblings like clear-session or save-paper, which are clearly different operations.

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 description implies the tool is for getting the current state of the research session, but it does not explicitly state when to use it versus alternatives. No exclusions or alternative tool names are provided, so guidance is implied rather than explicit.

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