refresh_page

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

With no annotations, the description must carry the full burden of behavioral disclosure. It clearly states that the action targets the current page, which is useful, but it does not disclose potential side effects like unsaved form data loss, behavior during page load failure, or whether the action waits for the reload to complete.

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 sentence with no filler or redundancy. It is front-loaded with the action and target, making it maximally scannable and efficient.

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 zero-parameter browser action, the description is largely complete for invocation: the action and target are unambiguous, and an output schema exists to cover return values. Minor gaps such as preconditions (browser must be open) and when to choose this over navigate are present, but they are not critical for a tool this simple.

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 tool has zero parameters, so the 100% schema coverage is vacuously satisfied. The baseline of 4 for a parameterless tool applies; no parameter details are needed in the description.

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 uses a specific verb, 'Refresh,' and a clear resource, 'the current page,' making the tool's function immediately understandable. It also distinguishes itself naturally from navigation siblings like go_back, go_forward, and navigate by naming a distinct browser action.

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 about when to use this tool versus alternatives, nor any mention of exclusions or preconditions. The description simply states what it does without providing situational context, so an agent receives no help deciding between refresh and other navigation tools.

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