get_dom_snapshot

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

With no annotations, the description is the sole source. It indicates a read operation ('Get'), but does not explicitly state safety, error handling, or performance implications. It mentions truncation behavior, which adds value, but lacks details like authentication requirements or side effects.

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 two sentences, front-loaded with the main purpose, and contains no extraneous information. Every sentence serves a clear role: stating the function and the truncation behavior.

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 the tool has 4 parameters, no output schema, and no annotations, the description adequately covers the core functionality and truncation. However, it lacks details on error cases (e.g., invalid selector) and could mention the tool's role in debugging, but overall it is sufficiently informative.

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%, but the description adds context: clarifying that selector targets a specific element and that maxLength controls truncation. This reinforces schema descriptions and provides functional meaning, though it does not introduce entirely new information.

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 outerHTML of a renderer page or specific element via selector. It uses a specific verb 'Get' and resource 'outerHTML', which distinguishes it from sibling tools like query_selector or evaluate_in_main. However, it does not explicitly differentiate from similar 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?

The description implies usage for getting HTML snapshots with optional element selection and truncation, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., query_selector or evaluate_in_renderer). No exclusions or prerequisites are mentioned.

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