Resume Research

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds the crucial non-obvious behavior: the session is persisted at start, so research continues server-side after the client disconnects, and results are retrievable once ready. It also discloses the dual behavior of the two call modes. It stops short of saying what is returned while a session is still running, which is the one remaining behavioral gap.

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?

Front-loaded with the core action, then conditions, then the no-arg/id distinction, then the handoff. Every sentence carries information, though the paragraph is longer than strictly necessary for a single-optional-parameter tool.

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 needn't be re-explained; the description instead covers the operational model that the schema cannot express. Both calling modes, the source of the id, and the downstream export path are all accounted for.

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 goes beyond the schema by explaining where the interaction_id comes from (the original research_deep call or list_research_sessions) and what happens when it is omitted.

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 specific verb and resource (resume a research_deep session) and scopes it to interrupted/in-progress sessions. It clearly distinguishes itself from research_deep (which starts a session) so an agent can route correctly without opening the schema.

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?

Gives explicit trigger conditions (client disconnect, transport error, cancellation) and a second legitimate use case (polling whether a long-running session completed). It also spells out the no-argument vs interaction_id branches and names both the sibling that supplies the id (list_research_sessions) and the natural follow-up (export_research_session).

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