browser_reload

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

With no annotations, the description carries the full burden of behavioral disclosure. It only restates the action ('reload') and adds no details about side effects (e.g., page reload may discard form inputs, trigger new network requests, or require an active session). The description does not go beyond what the tool name already suggests.

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 short sentence containing every essential piece of information. It is extremely concise and well-structured for the simplicity of the operation, with no wasteful words.

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 and no output schema, the description is minimally sufficient but lacks context about session requirements or behavior on failure (e.g., if no page is loaded). It could mention that it requires an active browsing session, but the overall complexity is low.

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 has one optional parameter (sessionId) with a description 'Browser session ID', achieving 100% schema description coverage. The tool description adds no extra parameter semantics, but the baseline of 3 applies since the schema fully covers the parameter.

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 ('reload') and resource ('current page'), clearly distinguishing it from sibling tools like browser_navigate or browser_go_back. It is immediately obvious what the tool does, even without additional context.

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 usage from its name and the fact that it operates on the current page, but it provides no explicit guidance on when to use it over alternatives like browser_navigate or browser_go_forward. No exclusions or alternative recommendations are given.

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