nex_browser_reload

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

With no annotations, the description carries the full burden and does disclose a real hazard: reloading can discard a filled form, so user confirmation is required. It also forbids specific workaround approaches (CDP, Python, image matching) for CAPTCHAs, which is meaningful behavioral context. It does not mention what happens to in-flight requests or session state.

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?

Three short sentences, front-loaded with the core action, with no wasted padding. The CAPTCHA sentence is slightly tangential but still earns its place as a guardrail.

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 trivial two-optional-parameter action with no output schema, this covers what the agent needs: what it does, the data-loss risk, and where to go for CAPTCHAs. Only the exact effect on page state is left implicit.

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 pageId and sessionId defaults are already documented in the schema. The description adds no parameter-level detail beyond that, so baseline 3 applies.

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?

"Reload the page" is a specific verb+resource that an agent can distinguish from navigate/go_back/go_forward in the sibling list. It doesn't explicitly contrast itself with those siblings, but the operation 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?

States a clear conditional guard (ask the user before reloading a filled form) and routes CAPTCHA situations to nex_browser_captcha_prepare. It lacks general when-to-use framing versus nex_browser_navigate, but the practical guidance is actionable.

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