browser_reload

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

With no annotations, the description carries the full burden. It does disclose one valuable behavioral trait — that previously captured element numbers are invalidated by the reload — but omits whether the call blocks until the page finishes loading, whether it bypasses cache, and whether unsaved form/input state is lost. For a state-mutating navigation tool this is a partial disclosure.

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?

Two short sentences with no filler, and the invalidation warning is front-loaded immediately after the action statement so an agent reads it before acting.

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 simple two-optional-parameter tool with full schema coverage and no output schema, the definition is close to sufficient and captures the key gotcha about stale element references. The notable remaining gap is load-completion semantics — whether the tool returns before or after the page has loaded — which materially affects agent sequencing.

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 100%, so tabId and windowId are already fully documented in the schema, including their defaults. The description adds nothing about targeting semantics, so the baseline of 3 applies.

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?

"Reload the tab" gives a specific verb and resource, and is clearly distinguishable from siblings like browser_go_back, browser_go_forward, and browser_navigate. It does not explicitly name those alternatives, but the action itself is unambiguous.

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?

Usage is only implied: an agent must infer that this is the tool to call when the page content needs refreshing rather than re-navigating. There is no explicit statement of when to prefer reload over browser_navigate or browser_go_back, and no prerequisites or exclusions.

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