browse_session_resume

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

Annotations indicate openWorldHint=true (the session may change externally) and this description goes beyond the annotations by explicitly mentioning 'after human action' and 'return current state', which signals that the tool waits for and reflects external state changes. It also implies the pause/resume flow, which is crucial behavioral context not apparent from annotations alone.

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 a single, concise sentence with no wasted words. It front-loads the essential action ('Resume a paused session') and includes the key output expectation ('return current state'), which is exactly what the agent needs.

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 has an output schema, rich parameter descriptions, and annotations, the description is sufficient. The only minor gap is not mentioning any specific return format details, but the output schema covers that. The description is complete for the tool's purpose and context.

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% with thorough parameter descriptions, especially captchaPolicy which details each enum value and the CAPTCHA_AUTONOMOUS behavior. The description says 'return current state' which aligns with the output schema. Although the description does not list parameters, the schema is rich and self-explanatory, so the description adds minimal but sufficient guidance.

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 uses a specific verb ('Resume') and resource ('a paused session'), and clarifies the return value ('return current state'). It distinguishes itself from sibling tools like browse_session_start, browse_session_snapshot, and browse_session_close by focusing on resuming a paused session after human action.

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 the context of use: after a human action, to resume a paused session. It does not explicitly name alternatives or exclusions, but the context is clear enough given the sibling set and the captchaPolicy pause option which connects to when this tool would be used.

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