reloadRefresh the active browser tab to load the current page content and reflect recent changes.
Reload the active tab.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "reload"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already define this as a mutable action (readOnlyHint: false). The description confirms this mutation ('Reload') but does not disclose further complex behavioral traits, placing it at a standard acceptable level for a simple function.
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 definition is maximally concise, consisting of a single, direct sentence that front-loads the action and target without any superfluous language.
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?
Given its zero-parameter complexity, the definition is complete. The agent needs only this single sentence to understand and invoke the tool correctly.
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?
Since the tool requires zero input parameters, the description adds no semantic value beyond the function title itself. For zero-parameter tools, this is considered adequate definition.
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 is exceptionally clear, using a specific verb ('Reload') and identifying the exact resource target ('the active tab'). This leaves no ambiguity for the agent regarding the tool's primary function.
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?
While it does not explicitly contrast itself against all sibling tools like 'forward' or 'back,' the action is fundamentally distinct from navigation, making its primary use case clearly implied by its name and context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.