reload

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 and falls far short. It never mentions that a reload discards unsaved form/JS state, whether it blocks until load completes, or how the optional timeout interacts with the operation.

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?

It is extremely short and front-loaded, with no wasted words, but this brevity comes at the cost of under-specification rather than being earned conciseness. Three words is arguably too little for a tool with a documented parameter and real side effects.

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 tool with a caveated parameter, no annotations, and no output schema, the description leaves critical gaps: side effects on page state, blocking behavior, and the meaning of timeout. It is not complete enough for reliable invocation.

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% and the description says nothing about the 'timeout' parameter, so an agent cannot know its unit, default, or whether it caps page-load waiting. It fails to compensate for the undocumented parameter.

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 phrase gives a specific verb ('Refresh') and resource ('the page'), so an agent can tell it is a page-reload operation. It offers no differentiation from near-siblings like navigate, go_back, or stop_loading, which all affect page navigation state.

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 indication of when to reload versus using navigate/reconnect, nor any prerequisite or side-effect warning. The agent must infer everything about selection from the name alone.

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