Browser Reload

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without mentioning side effects (e.g., losing form data, resetting JavaScript state, whether it waits for page load). It also ignores the tab and session parameters, which could affect behavior.

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, direct sentence that front-loads the action. It has no wasted words. However, it is under-specified, omitting essential usage and parameter context, so while concise, it is not as helpful as it could be.

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?

Despite being a simple tool, the description is incomplete. It doesn't explain when to use it, what the parameters do, or any caveats. The output schema exists but the description doesn't clarify the operation's scope or effects, leaving the agent under-informed.

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 description coverage is 0%, and the description says nothing about the 'tab' or 'session' parameters. An agent cannot infer their meaning, defaults, or interaction from the text, so the description adds no value over the bare schema.

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 states a specific verb ('Reload') and a specific resource ('the current page'). It clearly distinguishes from sibling tools like browser_navigate (loads a new URL) and browser_navigate_back/forward, so an agent can tell it apart.

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?

There is no guidance on when to use reload vs. navigate, back, or forward. It doesn't mention scenarios like refreshing after a change or handling stale content, nor does it exclude alternatives. The agent is left to infer usage.

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