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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It says nothing about mutation semantics, side effects, permissions, error handling, or return values for what is clearly an interactive/action-performing tool.

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?

Very short and front-loaded, but this is under-specification rather than conciseness. A five-word sentence cannot carry the required meaning for an 8-parameter interaction tool.

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?

With no annotations, no output schema, 8 parameters at 13% coverage, and an enum-free opaque `op` field, the description is nowhere near complete enough for an agent to call the tool reliably.

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?

Eight parameters with only 13% schema description coverage, and the description adds zero parameter information. The `op` discriminator, `ref`, `key`, `code`, `text`, and `input_method` are all undocumented in both places, leaving an agent unable to determine valid values or the relationship between 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?

"Interact via snapshot ref" gives a resource hint (snapshot refs) but the verb "interact" is generic and doesn't say what action is performed. Against siblings like browser_click, browser_fill, browser_type, and browser_press_key it's impossible to tell what this generic tool does that they don't.

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 when-to-use guidance, no exclusions, no mention of alternatives. The description offers no basis for choosing this tool over the many specific siblings (browser_click, browser_fill, browser_dom_input).

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