wait_for_gone

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

The description covers the core behavior (wait for removed/hidden) but does not discuss timeout behavior, error handling, or side effects. Without annotations, more detail on what happens on timeout or if element never appears would improve transparency.

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 extremely concise with two sentences, front-loading the purpose and immediate use case. No unnecessary 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?

For a simple tool with three parameters and no output schema, the description covers the main behavior and examples. However, it does not describe the return value or error conditions, which would be helpful given no output schema.

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?

All parameters have schema descriptions, so the description adds no additional meaning beyond what the schema provides. The schema already explains timeout, selector, and session_id adequately.

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 waits for element disappearance, specifying both removal from DOM and hiding. It distinguishes from sibling tools like wait_for_network by focusing on DOM element visibility.

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 mentions use cases (modals/dialogs/spinners), providing clear context for when to use it. It lacks explicit when-not-to-use guidance but still offers good differentiation from other wait tools.

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