browser_reload

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

The description provides minimal behavioral insight beyond the action itself. No annotations are present to compensate. Key behaviors like whether the reload bypasses cache or preserves page state are undisclosed.

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 very short and front-loaded, but it relies on an external reference ('see browser_docs') to provide necessary details. A self-contained description would be more efficient.

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 the existence of related navigation tools (browser_navigate, browser_go_back, browser_go_forward), the description fails to clarify how reload differs from those actions. It also omits any mention of side effects or page state.

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?

There are no parameters, and the schema coverage is 100% (empty). The description adds no additional parameter info, but this is not needed as the tool requires no configuration.

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 verb 'reload' and the resource 'current page'. It effectively distinguishes from sibling tools like browser_navigate or browser_go_back, which involve navigation to a different location.

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 on when to use this tool versus alternatives. It does not mention when a reload is appropriate (e.g., after dynamic content changes) nor when to use browser_navigate or browser_go_back instead.

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