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 behavioral disclosure. It discloses nothing about the reload behavior: whether it preserves session state, whether it waits for page load completion, whether it clears cache, or what happens to the current page snapshot. The statement 'Page reloaded.' only describes a result, not the action or its side effects.

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 short, but this is under-specification rather than conciseness. 'Page reloaded.' is a fragment that does not even form a complete imperative sentence, and it fails to convey the tool's purpose or usage. It earns no more than the bare minimum for being brief.

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 tool's low complexity, the description is still incomplete. It does not state what the tool does (reloads a page), what causes a reload, or what the outcome is beyond the past tense. The schema covers parameters, but the description lacks essential context about the action itself, making it insufficient for an agent to understand the tool.

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?

Schema coverage is 100% with both parameters (pageId, sessionId) described in the schema, so the baseline is 3. The description adds no additional meaning beyond the schema, but it also does not need to compensate since the schema already documents the parameters adequately.

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 'Page reloaded.' is a past-tense statement that simply restates the tool's name in a passive form, providing no specific verb or resource meaning. It fails to distinguish the tool from siblings like browser_navigate or browser_go_back, and gives no indication of what action the tool performs (e.g., reloads the current page).

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 on when to use this tool versus alternatives. There is no mention of when a reload is appropriate (e.g., after DOM changes, to fetch fresh content) or any exclusions relative to siblings like browser_navigate or browser_wait_for.

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