browser_get_zoom

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

No annotations are provided, so the description carries the full burden. It does disclose a real behavioral detail — the return encoding (1.0 = 100%), which matters because there is no output schema — but says nothing about what happens when tab_id is omitted, error behavior, or whether the value is per-tab or per-window.

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?

One short, front-loaded sentence with zero filler. The unit clarification is the highest-value piece of information and it is included without padding.

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 getter with no output schema this covers the return semantics adequately, but the only parameter is undocumented and the tool's tab-scoping behavior is unresolved, which an agent would need to know before calling it.

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 description coverage is 0% and the single parameter tab_id is never mentioned in the description. The crucial default behavior — that tab_id is optional and presumably falls back to the active tab — is left entirely undocumented.

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 ('Return') and resource ('the current zoom factor') and even disambiguates the unit convention (1.0 = 100%). It is clearly distinct from browser_set_zoom by name, but the description itself never names or contrasts that counterpart.

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?

The text gives no when-to-use, no conditions, and no mention of the obvious alternative browser_set_zoom. Usage is only inferable from the tool name, so this is effectively no guidance in the description body.

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