get_html

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

There are no annotations, so the description carries the behavior disclosure burden. It communicates a read operation but does not describe what kind of HTML is returned, whether the selector targets the first or all matching elements, or what the 'outer' behavior affects. An agent lacks key behavioral context beyond the tool name.

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 a single short sentence with no redundant wording or filler. It is front-loaded and easily parsed, though its brevity comes at the cost of detail covered by other dimensions.

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?

No output schema, no annotations, and 0% schema description coverage mean the tool requires a richer description. An agent cannot confidently determine what 'outer=false' returns, whether the default selector 'body' returns only the body element's HTML, or how this compares to related extraction tools.

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 does not explain either parameter. 'outer' is particularly ambiguous without explanation, and the description adds no meaning to 'selector' beyond the property name.

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 clear action and resource: getting HTML content from either the page or a selected element. It is specific enough to understand the tool's basic function, though it does not distinguish it from similarly named siblings such as get_text or get_attribute.

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?

No guidance is provided about when to use this tool instead of alternatives like browser_snapshot, get_text, inspect_element, or scrape_markdown. The description gives no context, prerequisites, or exclusions.

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