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

Beyond the annotations, the description discloses the return shape (full snapshot vs. outline), the escalation path for large pages, the wait-related latency tradeoff, and a security caveat that page text is untrusted data. The annotations already cover the mutation/safety profile (readOnlyHint=false, destructiveHint=false), so this description is adding genuinely useful context.

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 telegraphic sentences, zero preamble, with the primary action front-loaded and the routing/constraint information following. The compressed phrasing ("wait=load or idle for slow pages") is dense but unambiguous.

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?

With no output schema, the description correctly takes on the job of describing what comes back (snapshot vs. outline) and how to continue. The only omission is what happens when no tab is open or how the "current tab" relates to the tabs sibling, which forces a small inference.

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%, which sets a baseline of 3, and the description still adds meaning: it constrains url to public http(s) and explains when to pick wait=load or idle. It does not mention the snapshot parameter or the session_id/secret prerequisites in prose, but those are fully documented in the 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?

"Open a URL in the current tab" gives a specific verb, resource, and scope, and the sentence about small vs. big pages distinguishes this tool from the snapshot/find/read siblings that it feeds into. An agent can tell what this does and where it sits in the workflow without opening the schema.

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?

It routes the agent conditionally: small pages yield a full snapshot, big pages yield an outline and require find, read, or snapshot scope, and wait=load or idle is the answer for slow pages. It also states the domain restriction (public http(s) only). Lacks an explicit "don't use this when..." exclusion, so it stops just short of a 5.

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