browser_wait_for_element

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

No annotations provided, so description carries full burden. Discloses critical '[Disabled]' status upfront, explains polling mechanism ('Polls the page until...'), and clarifies timeout behavior. Missing detail on what happens when timeout expires (exception vs null return).

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?

Four sentences with zero waste. Critical '[Disabled]' status is front-loaded. Logical flow: status → core action → mechanism → use case → parameter tip. Appropriately sized for complexity.

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?

Missing output schema documentation (what is returned when found vs timeout). With no annotations and 4 parameters, description adequately covers mechanism and intent but should specify failure modes and return structure for full completeness.

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 has 100% description coverage, establishing baseline 3. Description adds minor semantic context for 'visible' parameter (CSS visibility concept) but largely mirrors schema content. No additional syntax or format guidance beyond schema.

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?

Clear specific verb ('Wait') and resource ('element matching CSS selector'). Distinguishes from sibling query tools by emphasizing polling behavior and SPA/async use cases. The '[Disabled]' prefix is cryptic but doesn't obscure the core purpose.

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?

Provides positive usage context ('For SPAs where content loads asynchronously') but lacks explicit when-not-to-use guidance or named alternatives (e.g., when to use browser_query_elements instead for immediate checking).

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