reload

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

Description mentions preserving init scripts, which provides some behavioral context. However, with no annotations, it lacks disclosure of other effects (e.g., state reset, cookie clearing). The info is adequate but incomplete.

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?

Single sentence is concise and front-loaded. However, it omits essential parameter guidance, which could be added briefly without bloating.

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 with one optional parameter and no output schema, the description is nearly complete but misses parameter explanation. It adequately covers the primary function.

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 has one parameter (wait_until) with default but no description. The description does not mention the parameter at all, failing to compensate for 0% schema coverage. The agent cannot infer valid values or meaning.

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?

Description clearly states the action (reload) and resource (current page), and adds distinguishing detail about preserving init scripts. This differentiates it from siblings like navigate or close_browser.

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?

No guidance on when to use this tool versus alternatives (e.g., navigate, close_browser). No mention of prerequisites or when not to use it.

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