browser_reload

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It simply states the action without detailing side effects like losing page state, waiting for load, or how the optional 'hard' parameter affects behavior. This is a significant gap for a navigation/mutation tool.

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?

The description is a single, concise sentence that directly states the tool's purpose. It's front-loaded and contains no filler, following best practices for minimal relevant information.

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 tool with one optional parameter fully documented in the schema, the description adequately covers the core function. However, given the lack of annotations and output schema, a brief mention of behavioral context (e.g., page state loss) would make it more complete. Still, the tool's simplicity raises the acceptable bar.

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?

The input schema documents the 'hard' boolean parameter with description 'Bypass cache', covering 100% of parameters. The description itself adds no parameter information beyond what the schema provides, 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?

The description 'Reload the current page' uses a specific verb and resource, clearly distinguishing it from sibling navigation tools like browser_navigate, browser_go_back, and browser_go_forward. The action is unambiguous and unique among the siblings.

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 clear usage context: use it when you want to reload the current page. It doesn't explicitly mention alternatives or exclusions, but for a simple reload action, the context is sufficiently clear and there are no competing tools that perform the same function.

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