browser_reload

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

The description states the core effect plainly: the current page is reloaded. However, with no annotations to rely on, it does not disclose any additional behavioral traits such as whether the active tab is targeted, whether page state is lost, or whether the tool waits for the reload to finish. The simplicity of the action keeps this from being a lower score, but there is room for more transparency.

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, complete sentence with no unnecessary words. It is front-loaded and immediately comprehensible. No filler or redundant information is present.

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?

Given that the tool has no parameters and an output schema is present, the description is nearly sufficient. The only missing context is guidance on when reloading is appropriate and whether there are side effects on the page state. Still, for a simple command like this, the definition is close to fully adequate.

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 tool has zero parameters, so the description does not need to explain parameter behavior. The schema coverage is effectively 100% because there are no properties to document. This is a reasonable baseline score for a parameterless tool.

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 clearly states a specific action ('reload') on a specific resource ('the current page'), which aligns directly with the tool name. It is understandable without needing to inspect the schema. However, it does not explicitly distinguish itself from related navigation tools like browser_navigate or browser_go_forward, though the meaning is still 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?

The description provides no guidance about when to use this tool versus alternatives such as browser_navigate, browser_go_back, or browser_go_forward. It also omits context like whether the page needs to be loaded first or what happens if the browser is not connected. There is no stated best use case, so agents must infer the intended usage from the name alone.

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