get_html

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not what HTML is returned (outerHTML of the matched node?), not whether it is a live read or a cached snapshot, and not the interaction with frames or page state. "(alias)" adds ambiguity rather than behavior.

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 words is short, but this is under-specification rather than conciseness — nothing is front-loaded because nothing is stated. The parenthetical alias note consumes space without conveying information.

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 two-parameter retrieval tool with no annotations and no output schema, the description supplies none of the missing context: no return shape, no selector syntax, no semantics for outer, and no routing away from near-identical siblings.

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 0% and the description explains neither parameter. The required selector and the boolean outer (which presumably toggles outerHTML vs innerHTML) are left entirely undocumented, so the agent must guess the meaning of the only optional flag.

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?

"Get HTML" names a verb and a resource, but "(alias)" is cryptic — it does not say what it is an alias of, nor how it differs from siblings like get, get_text, get_attribute, or get_page. An agent cannot distinguish this tool's actual purpose from the surrounding retrieval tools.

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 use this tool versus get_text, get_attribute, get, or get_page, all of which sit in the same sibling cluster. The "(alias)" note hints at duplication but never names the primary tool or the condition that selects it.

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