browser_reload_tab

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that bypass_cache produces a hard reload, which adds real value, but says nothing about which tab is affected when tab_id is omitted, whether the reload waits for load completion, or how navigation state is affected.

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?

Two short sentences, action first and the parameter hint second. Nothing is padded or redundant.

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 mutation tool with no annotations and no output schema, the definition is thin: the tab-targeting semantics of tab_id (and its null default) and the post-reload state are unaddressed, leaving the agent guessing about scope.

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%, so the description must compensate. It clarifies the effect of bypass_cache ('hard reload'), which is genuinely beyond the schema's bare boolean, but leaves tab_id undocumented — it is unclear whether null means the active tab or an error.

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?

States a specific verb+resource combination ('Reload a tab') that is distinct from adjacent siblings such as browser_navigate, browser_back, browser_forward, and browser_new_tab. It does not explicitly name what it is not, but the action is unambiguous.

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 prefer this over browser_navigate, browser_back, or browser_wake_tab, and no mention of prerequisites. The description only says what the tool does, not when to reach for it.

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