session_wait

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'wait for a condition' and does not explain what happens on timeout, whether it throws or returns a status, whether it polls, or what the return value is. This is a significant transparency gap for a tool that can block for an arbitrary duration.

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?

One compact, front-loaded sentence communicates the core behavior and enumerates the condition types without 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 no annotations and no output schema, the description is too thin. It omits the default timeout, failure behavior, return value, and the meaning of tabId. An agent cannot reliably know whether a timed-out wait is an error or a normal outcome, which is essential for correct invocation.

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 50%, so the description needs to add meaning for undocumented parameters. It does clarify condition by naming the three modes and explains value as a URL substring or selector, but it leaves tabId completely unexplained and does not clarify the dependency between condition and value (e.g., value is unused for 'load').

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 precisely what the tool does: it waits for one of three conditions (load, URL match, selector presence). The verb 'wait' plus the condition types make the operation unambiguous and distinct from sibling navigation/read/snapshot tools.

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 condition enum implies usage (e.g., wait after navigation or before interacting with a selector), but there is no explicit guidance on when to prefer this over alternatives, nor any mention of why one might choose it over session_health or polling via snapshot. Usage is inferable rather than stated.

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