reload

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

With no annotations, the description carries the full burden. It does not state whether the call blocks until the page finishes loading, whether it discards unsaved form state or scroll position, or whether it requires the tab to be focused. Those are exactly the behaviors an agent needs before triggering a reload.

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 four-word imperative sentence, front-loaded and waste-free. It is arguably too terse for the behavior it triggers, but there is no structural or verbosity problem.

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 is simple (one optional param, no output schema, no nested objects), so the description is close to adequate. It still leaves open the load-wait and state-loss questions, which matter for a reload operation but are lower-stakes than for a complex tool.

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?

There is one optional parameter (tab) and the schema documents it at 100% coverage, including its 'defaults to current' behavior. The description adds nothing about the parameter, which is acceptable given the schema baseline, but it misses the chance to clarify current-tab versus background-tab semantics.

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" names a specific verb (reload) and resource (the current page), so an agent immediately knows the operation. It does not distinguish itself from related siblings such as navigate, back, or forward, which is the only thing keeping it from a 5.

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?

The description gives no guidance on when to reload versus using navigate/back/forward, nor any exclusions or preconditions. The agent must infer usage entirely from the tool name.

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