browser_get_dom

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

No annotations are provided, so the description bears full responsibility. It fails to disclose that the operation is safe/read-only, what format the DOM structure is returned in (e.g., HTML string, object), or any potential performance impact. The single sentence provides minimal behavioral insight.

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?

Extremely concise at one sentence, but clarity is sacrificed. Key information (return format, usage nuances) is omitted. It earns its place as a brief description but lacks structure and front-loading of essential details.

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, the description should explain what is returned (e.g., HTML string, JSON structure). It does not, and the 'see browser_docs' reference is insufficient. For a simple tool with one param, the description is incomplete.

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% with one optional parameter 'selector'. The description adds 'or specific element data,' reinforcing that the selector narrows the result. This adds minimal meaning beyond the schema, justifying the baseline score of 3.

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 verb 'Get' and the resource 'DOM structure or specific element data', distinguishing it from similar tools like browser_get_text and browser_read_page. The reference to browser_docs provides additional context, though the description could be more self-contained.

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 on when to use this tool versus siblings like browser_get_text or browser_read_page. The 'see browser_docs' mention implies further instructions elsewhere, but the description itself offers no criteria for selection or exclusions.

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