browser_get_dom

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

With no annotations, description handles behavioral disclosure well. Describes return content and performance comparison to screenshots. Could mention it's read-only and no side effects, but acceptable.

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?

Pithy two sentences covering purpose, usage, and key benefit. Front-loaded with action.

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?

Covers purpose, usage, and output nature. No output schema needed. Could differentiate from browser_get_page_info but overall complete for a read-only DOM retrieval tool.

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% and description adds no extra parameter details beyond the schema fields.

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?

States it gets page DOM structure, returns interactive elements with text/roles/positions. Clearly distinguishes from screenshots by claiming it's faster and more detailed.

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 says it's the primary way to understand the page for finding clickable elements, reading text, and understanding layout. Mentions it's faster and more detailed than screenshots, but doesn't discuss when to avoid it.

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