Pause for Human

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

With no annotations, the description carries full burden. It discloses that the session is paused and waits for human, but omits details like potential timeouts, how the pause is reflected, or that it can be resumed. The core behavior is clear, yet lacks depth for an agent to fully anticipate side effects.

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, front-loaded sentence that conveys the action and purpose with zero wasted words. It is highly concise and well-structured.

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?

The tool is simple, but with 3 required parameters and no parameter descriptions in the schema, the description is somewhat incomplete. It does not explain the workflow (e.g., that get_human_wait_state can check status or resume_session can continue), leaving gaps in contextual guidance.

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 should compensate. It does hint at the 'reason' parameter via examples (LOGIN_REQUIRED, MFA_REQUIRED, CAPTCHA_REQUIRED), but it does not explain 'sessionId' or 'instructions' (e.g., that instructions are the message shown to the human).

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 states the tool's purpose: 'Pause the session and wait for human' with concrete examples (login, MFA, captcha). It uses a specific verb and resource, distinguishing it from sibling tools like resume_session and wait.

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 examples of login/MFA/captcha strongly imply when to use this tool—whenever human intervention is required. However, it does not explicitly mention alternatives or when not to use, such as comparing to browser.wait or automatic handling.

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