browser_reload

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

No annotations exist, so the description bears the full disclosure burden, yet it only restates the cache-bypass option already in the schema. It says nothing about whether the call waits for the page load event, how in-flight requests or POST re-submission are handled, or what the tool reports back.

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 sentence, front-loaded with the action and immediately qualified by the optional variant. No wasted text.

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 one-parameter optional tool this is nearly sufficient, but with no output schema and no annotations, the description should at least hint at what the call returns or whether it resolves after the page finishes loading.

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% and the single optional `hard` parameter is fully documented in the schema. The description's phrase 'hard refresh (cache bypass)' merely echoes that schema text without adding behavior details such as whether a hard reload also bypasses service workers.

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 (reload) and resource (current browser page), plus the optional hard-refresh variant. It is unambiguously distinct from siblings like browser_navigate, browser_go_back, or browser_go_forward.

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 action is self-explanatory, so correct usage is implied, but the description never states when to prefer reload over browser_navigate (e.g., re-requesting the same URL) or that it acts on the active tab. No exclusions or alternatives are named.

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