Reload the current page, waiting until the page fully loads or network activity is idle.
Reload the current page. waitUntil 'load' (default) or 'networkidle'.
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": "veil_reload"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| waitUntil | No |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description minimally discloses the waitUntil option but does not mention potential destructive effects (e.g., losing form state) or behavior beyond reloading. Lacks depth for a mutation action.
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?
Two sentences, front-loaded and no waste. Could benefit from slight structural improvement (e.g., separating parameter explanation) but remains 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 simple reload action with one parameter, description is fairly complete. Lacks only behavioral context about potential hanging with networkidle, but overall adequate given tool simplicity.
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?
Single parameter with enum is fully explained: both 'load' and 'networkidle' values are listed, and default is identified. Since schema coverage is 0%, description compensates completely.
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?
Clearly states 'Reload the current page' with a specific verb and resource, distinguishing from sibling navigation tools like veil_goto, veil_back, and veil_forward.
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?
Implies usage for reloading, but no explicit context on when to use vs alternatives like veil_goto (which navigates to a URL) or wait conditions. Missing when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.