nex_browser_reload

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, 'Page reloaded.' tells the agent nothing about what happens upon invocation—whether it reloads the current page, discards unsaved changes, requires network, or returns a confirmation. There is virtually no behavioral transparency.

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 extremely short, but this is under-specification rather than effective conciseness. It lacks essential information and reads as a status message rather than a tool description. Front-loading is irrelevant when the content is nearly empty.

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 simple reload action, a minimal description could still be complete if it clearly stated 'Reloads the page.' However, 'Page reloaded.' is a past-tense statement that does not even confirm the tool's action, nor does it explain behavior, return value, or any caveats. With no output schema and no annotations, this is grossly incomplete.

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?

The input schema covers both parameters (pageId and sessionId) with descriptions, and the schema description coverage is 100%. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 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?

The description 'Page reloaded.' is a statement of completion rather than a clear imperative describing what the tool does. It essentially restates the tool name (reload) in past tense, providing no detail on scope or effect, and does not distinguish from sibling navigation tools like go_back or navigate.

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 this tool versus alternatives such as go_back, go_forward, or navigate. The description offers no context, prerequisites, or exclusions, leaving the agent without direction on selecting this tool appropriately.

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