get_page_html

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

Discloses truncation behavior and return of HTML string(s). However, lacks details on performance impact, error handling, or behavior if selector matches many elements. No annotations provided.

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 concise sentences covering functionality, usage examples, and selector constraint. No extraneous words.

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?

Does not specify return format clearly ('HTML string(s)' ambiguous; single vs array). Also lacks error handling or edge case details. Output schema absent, so description carries more burden.

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?

Adds value beyond schema by clarifying that selector is optional and returns full page HTML when omitted, and specifies 'Standard CSS selectors only.' Schema coverage is 100%, baseline 3, elevated by added context.

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?

Description specifies returning raw outerHTML of matching elements or full page HTML if no selector, truncated to max_length. Distinguishes from siblings like get_page_elements and web_fetch.

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?

Provides clear use cases (inspect component/markup structure, SEO meta tags, widget DOM) but does not explicitly state when not to use or mention alternative tools.

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