oc_session_resume

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

The description discloses that the tool reads the last snapshot and checks live tabs, implying a non-destructive read operation. Annotations (readOnlyHint: false, destructiveHint: false) are neutral; the description provides additional context about the behavior without contradictions.

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 three sentences long, front-loading the primary action and then detailing the process and calling action. Every sentence is informative and there is no redundancy or 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?

Despite lacking an output schema and having minimal annotations, the description explains the output structure (resume guide with objective, progress, tab status) and the conditions for use (after compaction). It provides enough context for an agent to understand when and how to invoke the tool, though more detail on side effects could be added.

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 input schema covers both parameters with descriptions (snapshotId and taskId), achieving 100% coverage. The tool description does not add new information about the parameters beyond summarizing their roles; it only generalizes that it reads the latest snapshot. Thus, the description does not significantly enhance understanding beyond the schema.

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 identifies the tool's purpose with a specific verb ('Restore working context after context compaction'), details the process (reads snapshot, checks tabs), and specifies the output (resume guide with objective, progress, tab status). It distinguishes itself from sibling tools like oc_session_snapshot by focusing on restoration rather than capture.

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 explicitly states when to use the tool ('Call this after compaction to continue where you left off'). It implies the context of use, but does not explicitly exclude other scenarios or mention alternatives, though the sibling list includes related tools like oc_session_snapshot.

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