session_resume

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

With no annotations provided, the description discloses return behavior ('Returns: Session state') and a warning condition ('warns if the bound document is no longer open'). It also implies disk I/O via 'from disk.' This goes beyond a bare description, though it doesn't discuss side effects or prerequisites in detail.

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 concise and well-structured, front-loaded with the primary verb phrase, then an Args section, and a Returns section. Every sentence serves a purpose; no wasted words.

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 the tool's simplicity (one parameter, output schema present), the description adequately covers action, parameter semantics, and a key behavioral caveat. It could clarify whether resuming activates the session or impacts the current environment, but the current level is sufficient.

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%, so the description compensates by explaining that session_id is 'The session to resume (see session_list),' providing a cross-reference to another tool for valid values. This adds meaning beyond the raw schema field type, though it could include more detail on format or constraints.

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?

Description begins with 'Resume a paused/completed session from disk.' This clearly specifies the action (resume) and the resource (a paused/completed session), with 'from disk' adding scope. It differentiates from siblings like session_pause, session_start, and session_complete, which serve different purposes.

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 usage context: you should use this when you have a paused or completed session to resume. It also directs the user to session_list for obtaining valid session IDs, which is helpful. However, it does not explicitly state when not to use it or mention alternatives like session_start or session_rollback.

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