assert_visible

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

Discloses the oracle ladder, the 'unverifiable' error for non-inspectable WebViews, and substring matching behavior for WebView innerText, all beyond what annotations (none provided) would cover.

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?

Three efficient sentences front-load the core action and add necessary detail without redundancy.

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?

Covers key behaviors and parameter guidance, but lacks explicit return value description or comparison with assert_text. No output schema exists.

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%, but the description adds value by explaining oracle ladder, error behavior, and clarifying that WebView text is always substring despite the 'contains' default.

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 it asserts visibility of an element/text via a specific oracle ladder, differentiating it from siblings like assert_not_visible and assert_text.

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 context on when to use (text or selector) and describes behavior for unverifiable WebViews, but does not explicitly exclude alternatives or compare with assert_text.

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