Do something on the page

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

Annotations are empty, so the description carries the full disclosure burden. It usefully warns that this acts in a real logged-in browser and fills/submits actual forms, which is important mutation context. However, it does not cover error behavior, tabId semantics, limits, or the fact that the invoked capability may itself be destructive.

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 two short sentences, front-loaded with the core invocation rule and followed by an important real-browser caveat. Every sentence contributes without padding.

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 complex meta-tool with arbitrary nested args, no annotations, no output schema, and no sibling-specific routing guidance, the description is too sparse. It omits when to use this versus direct browser tools, how tabId affects execution, and what the caller should expect in return.

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 67%, and the description mostly repeats what the schema already states: tool names come from browser_capabilities and args match the target inputSchema. It adds no meaningful detail for tabId and little beyond the schema for the nested args object.

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 states a specific action: call one of the tools reported by browser_capabilities, passing arguments that match that tool's inputSchema. It also clarifies that execution happens in the real logged-in browser and submits actual forms. It is clear about the meta-invocation purpose, though it does not explicitly distinguish when this indirect route should be used instead of the many direct browser_* siblings.

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?

There is no explicit when-to-use guidance beyond the implied instruction to call a tool listed by browser_capabilities. The description does not say when to prefer browser_invoke over direct siblings such as browser_click or browser_fill, nor does it state prerequisites or exclusions.

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