chrome_use_reload

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about what a reload destroys (unsaved form input, element refs), whether it re-issues network requests, or whether it waits for the load to complete before returning. For a state-mutating navigation tool in this family, that is a significant disclosure gap.

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?

A single front-loaded sentence with zero filler. It is efficient, though the terseness contributes to the gaps in usage and behavioral coverage rather than reflecting deliberate restraint.

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 has no annotations and no output schema, so the description must supply all behavioral context; instead it omits waiting behavior, effect on element refs, and page-state loss. Even for a simple reload action, an agent driving a browser needs to know whether the call returns before or after load completes.

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%, and the parameters (observe, session, timeoutMs) are documented in detail in the schema, including the chrome-use CLI flags they map to. The description adds nothing beyond that, so the baseline 3 is appropriate.

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 (reload) and resource (the current page), which is unambiguous on its own. It does not distinguish itself from navigation siblings such as chrome_use_back or chrome_use_forward, though the verb 'reload' is distinctive enough that confusion is unlikely.

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 is given on when to reload versus using chrome_use_back/forward/open, nor on prerequisites such as a page being open. The agent must infer all usage conditions from the one-line purpose statement.

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