wait_for_browser_feedback

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

No annotations are provided, so the description carries the full burden, and it does disclose the key trait: this is a blocking call that waits for a user submission. It also lists the returned payload (screenshot, element info, console logs, description). It omits what happens on timeout expiry, which is a meaningful gap for a blocking tool.

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?

Front-loads the blocking behavior and return payload, then flags the critical usage warning. Slightly long, but every sentence carries operational value and nothing is repeated from the schema.

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?

With no output schema and no annotations, the description must cover both behavior and returns, and it does so well. The only missing piece an agent might need is timeout-expiry behavior, which is not addressed.

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% and the single timeout_seconds parameter is fully documented inline with its default. The description adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 a specific verb+resource (wait for browser widget feedback) and enumerates what it returns. It is clearly distinguishable from siblings like get_pending_feedback and wait_for_multiple_feedback, which do not block for a new submission.

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?

Gives explicit when-and-when-not guidance: after receiving feedback, do NOT re-call; instead act on it, and only re-call if the user asks or you need to verify a fix. This directly routes the agent away from a common misuse.

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