get_research_session

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

Beyond the readOnly/idempotent annotations, the description adds rich behavioral context: the lastSteps sliding window, the 1-indexed foundInStep semantics with no step 0, and the 4-hour session persistence across restarts. This is exactly the kind of behavioral disclosure agents need.

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 front-loaded with the primary purpose and then packs edge-case details into a compact, well-structured paragraph. Every sentence contributes meaningful information—no filler or repetition.

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 that the output schema is present and the tool has only two simple parameters, the description is complete. It covers return contents, sliding-window behavior, source-to-step attribution, and retention policy, leaving no significant ambiguity.

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%, so the baseline is 3. The description adds modest value by explaining that stepId retrieves earlier steps and sessionId identifies the session, but the schema already contains equivalent descriptions. No parameter enums or complex semantics require extra explanation.

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 opens with a specific verb and resource: 'Recover a sequential_search research session after context loss.' It clearly distinguishes the tool from siblings like sequential_search (which likely creates/continues sessions) by specifying the recovery use case.

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 clearly states when to use the tool ('after context loss') and explains how to fetch earlier step details. It does not explicitly name alternative tools or when-not-to-use scenarios, but the context is sufficiently clear.

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