reload_tab

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

Beyond annotations, the description discloses two important behaviors: it waits for the page to fully load before returning, and it waits for AgentScript/WebMCP tools to re-register. This is genuinely useful stateful behavior that an agent could not infer from the schema or annotations.

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?

Three short sentences with no filler: purpose, usage context, and blocking behavior are each given exactly one sentence. The most important information is front-loaded.

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 single optional-parameter utility, the description covers what it does, when to use it, and its blocking/registration behavior. No return value or output schema is needed for an operation whose main result is the reload itself.

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 coverage is 100% and the only parameter, tabId, is already documented as defaulting to the active tab. The tool description adds no additional parameter semantics, which is acceptable given the high schema coverage.

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 opens with a specific verb and resource — 'Reload a browser tab' — and adds the precise purpose 'to re-inject updated userscripts.' This clearly distinguishes it from siblings like open_tab, close_tab, and focus_tab.

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?

It explicitly says to use this tool after export_script to see the effect of changes, giving a concrete workflow context. It does not mention when not to use it or name alternatives, so it falls just short of full usage guidance.

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