html

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

No annotations are provided, so the description carries the full disclosure burden. It implies a read operation but does not state what happens when the element is missing, whether refs expire after navigation, how large the returned markup may be, or how the call interacts with the tab/session — all meaningful for a browser-inspection tool.

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?

It is short, but this is under-specification rather than conciseness: a four-word noun phrase with no verb and no front-loaded cue about which parameter to use. Brevity here costs the agent actionable context.

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 four optional parameters, no annotations, and no output schema, the description should at minimum say how the target element is identified (ref vs selector) and roughly what comes back. Neither is covered, so it is not complete enough to call reliably.

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%, so each of ref, selector, tab, and request_timeout is already documented in structured fields, making 3 the baseline. The description adds nothing beyond that — notably it does not resolve the real ambiguity that all four params are optional, leaving unclear whether ref or selector (or neither) is required to identify the element.

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 fragment "outerHTML of an element" identifies the resource returned but omits an explicit verb and gives no differentiation from close siblings such as text (inner text), attr (attribute values), or eval. An agent can infer it retrieves serialized HTML markup, but only by inference.

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 guidance on when to choose this over text, attr, or eval, and no mention of when NOT to use it (e.g., for large subtrees where text or a targeted attr call would be cheaper). Nothing tells the agent which of ref or selector to supply.

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