browser_reload

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

The description does not disclose potential side effects such as loss of form data or reliance on cache. While the parameter description mentions cache behavior, the tool description itself omits behavioral details that could affect the user.

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 extremely concise—a single sentence—and directly states the purpose without any unnecessary words. It is appropriately sized for the simple action and front-loaded with the core action.

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 browser action, the description is adequate: it clearly specifies the target ('current page') and the action. It could benefit from mentioning that it operates on the active tab, but given the simplicity and sibling context, it is largely complete.

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 schema provides full coverage for the single parameter (ignoreCache) with a clear description. The tool description adds no extra meaning beyond the schema, aligning with the baseline of 3 for high schema coverage.

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 the action: 'Refresh the current page.' It names the specific verb (refresh) and the object (current page), making it unambiguous and distinct from sibling tools like browser_reset or browser_newTab.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of appropriate contexts or scenarios where refreshing is necessary or preferable.

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