browser_set_page_zoom

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

With no annotations, the description carries full disclosure burden, yet it only clarifies the scale format. It never says whether the change is per-tab or global, whether it persists across navigation, or whether it requires an active page, all of which an agent would want to know.

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?

Single front-loaded sentence with parenthetical examples; nothing wasteful, and the key semantic detail is embedded compactly.

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?

For a trivial one-parameter setter with no output schema, the description is mostly adequate, but it omits the behavioral context (scope/persistence) that would fully equip an agent to invoke it correctly.

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%, so baseline is 3, but the description adds genuine meaning beyond the schema's bare 'Zoom scale factor' by mapping concrete values (0.5=50%, 1.0=100%, 1.5=150%), removing unit ambiguity.

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 a specific verb+resource ('Adjust page zoom level') that is clearly distinct from other browser_set_* siblings. It does not explicitly name an alternative, but the resource is unique enough that no differentiation text is needed.

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?

There is no statement of when to use this tool versus e.g. browser_set_viewport or browser_zoom-like alternatives, and no prerequisites (such as requiring a loaded page). Only the name implies usage.

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