browser_hard_reload

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

With no annotations, the description carries the behavioral disclosure burden and covers key traits: cache bypass, acceptance of beforeunload prompts so the reload actually happens, and the reported output. It omits potential details like whether it waits for load completion or clears cache, but overall it is transparent.

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?

Three tight sentences, each adding distinct information: the core action, the beforeunload handling, and the return values. No filler, repetition, or unnecessary details.

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 low-complexity tool with no annotations or output schema, the description adequately explains the action, a key behavioral nuance, and the return value. The main gap is the undocumented sessionId parameter, but the tool remains invocable with no required parameters.

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 description never mentions the sessionId parameter. The agent only gets the parameter name and optionality as a clue; there is no guidance on when to pass it or what session is used by default.

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?

Description states a precise action ('Reload the page bypassing cache'), gives a familiar user analogue (Cmd+Shift+R), and specifies the output (reloaded page's url and title). This clearly distinguishes it from normal navigation tools like page_goto or cache-clearing tools like browser_clear_cache.

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 description implies when to use it (when a cache-bypassing reload is needed) via the 'hard refresh' analogy, but it does not explicitly contrast it with alternatives or state when not to use it. No sibling tool is named, leaving the agent to infer the appropriate context.

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