stop_loading

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether an in-progress navigation is cancelled or merely paused, not what happens if no load is active, and not whether it throws or returns silently. "Stop loading" adds no context beyond the name.

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 words are technically concise but this is under-specification rather than efficiency, mirroring the LOW calibration case for a single-word description. Nothing is front-loaded because nothing is said.

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 zero-parameter control tool with no annotations and no output schema, the description should at minimum state what is stopped, what happens to the pending navigation, and any follow-up expectations. None of that is present, leaving the agent to guess.

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?

The tool takes zero parameters and the schema is empty with 100% coverage, so there is nothing for the description to document. The baseline of 4 applies for a parameterless tool.

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 "Stop loading" merely restates the tool name and adds no further specificity. It does convey a verb+resource pair by implication (stop an in-progress page load), but it does not differentiate this from siblings like wait, wait_for, reload, or navigate, all of which relate to load state.

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?

There is no guidance on when to call this versus waiting tools (wait, wait_for, wait_for_text) or navigation controls (navigate, reload, go_back). An agent must infer that this aborts an in-flight load, with no stated preconditions or exclusions.

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