browser_reload

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

There are no annotations, so the description must fully communicate behavior, but it only restates the action without noting side effects, whether it waits for the page to load, how failures are handled, or that reloading may lose unsaved form state. This is a meaningful gap for a browser action.

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 focused sentence with no wasted words. It immediately conveys the core operation and is appropriately front-loaded.

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?

The tool is simple and its parameters are fully documented, but with no annotations and no output schema, the description provides only the bare minimum. It does not explain post-reload behavior, error conditions, or when the action completes, leaving some ambiguity for an agent.

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 100%, so both tabId and agentId are already documented in the schema. The description adds no additional parameter semantics beyond the generic phrase 'specified tab,' which earns the baseline score.

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 clear verb and resource: 'Reload the page in the specified tab.' This is concise and distinguishes the tool from siblings like browser_navigate or browser_snapshot by naming the specific action of reloading.

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 use case is implied: call this when you want to refresh/reload the current page in a tab. However, it does not explicitly state when not to use it or mention alternatives such as browser_navigate or browser_navigate_forward, so the guidance is minimal.

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