browser_list_clickables

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

With no annotations provided, the description carries the full burden. It discloses that only visible clickables are listed, that listing is frame-scoped, and that various filters are supported. This covers key behavioral traits, though it does not mention return format or potential side effects (which are minimal for a list operation).

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?

Two tight sentences with no redundancy. The first sentence states the core function, the second lists filter options and the use case. Every word earns its place.

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 tool with 9 parameters and no output schema, the description provides sufficient context for selection and invocation: it names the resource, timing, and main filter dimensions. It does not describe the return structure, but parameter details are fully covered in the schema, so overall completeness is good.

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 description coverage is 100%, so baseline is 3. The description adds value by grouping filter options (role+name, text, css, enabledOnly, scopeCss) but doesn't elaborate on parameters like timeoutMs or includeBoundingBox beyond what the schema already provides.

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 begins with a clear, specific action: 'List visible clickable elements (buttons, links) in a frame.' It also distinguishes this tool from the sibling browser_snapshot by adding 'Use to discover what to click without snapshot.'

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 closing phrase 'Use to discover what to click without snapshot' gives clear context for when to use this tool. It implicitly differentiates from browser_snapshot but does not explicitly state when not to use it or name alternative tools.

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