browser_compare_dom

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

No annotations are provided, and the description fails to disclose whether the comparison is read-only, what side effects exist, or what the output represents. The schema shows inputs but the description gives no behavioral context, leaving the tool's runtime behavior completely unspecified.

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 a single 5-word sentence, extremely concise and front-loaded. It avoids unnecessary words while clearly stating the core action, making it a model of brevity.

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 complex nested input schema and lack of output schema, the description is far too minimal. It doesn't explain what the comparison yields, any constraints (e.g., same page), or how errors are handled. The tool requires two structured snapshot objects, and the description provides no guidance on using them.

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?

The description says 'two compact DOM snapshots,' which loosely maps to the 'before' and 'after' parameters. However, it doesn't explain the expected relationship between the snapshots, the meaning of 'compact,' or how the parameters are interpreted. With 0% schema coverage, this is insufficient.

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 uses the verb 'Compare' with the resource 'two compact DOM snapshots,' clearly identifying the tool's core function. It is distinct from sibling tools like browser_get_dom_snapshot, as none other indicates comparison. However, it lacks specificity about what type of comparison (e.g., structural, textual) is performed.

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 is provided on when to use this tool or how it relates to alternatives. The description doesn't mention prerequisites such as taking snapshots first or comparing before/after states, leaving the usage context undefined.

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