browser_get_outer_html

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

No annotations provided, but description discloses raw HTML output, token expense, and truncation to maxLength. Could mention absence of side effects but sufficient given 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?

Three focused sentences: purpose, usage guidance, and output limitation. No redundant text, though slightly verbose with 'DEBUG FALLBACK' label.

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?

Given no output schema and no annotations, description covers purpose, usage context, and truncation. Lacks explanation of return format but name implies raw HTML.

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%. Description adds value by explaining default maxLength, optional backendNodeId meaning, and truncation behavior beyond 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?

The description clearly states the tool retrieves raw outerHTML of a DOM element by backendNodeId, with a fallback to document root. It distinguishes itself from sibling get_semantic_surface as a debug fallback.

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?

Explicitly advises when to use (when get_semantic_surface returns empty tree) and when not (prefer get_semantic_surface). Includes warning about token cost and positions it exclusively for debugging.

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