browser_stop_loading

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

With no annotations, the description carries the full disclosure burden. It does add real value by scoping the effect to page loading and disclaiming any impact on running tasks, but it does not say what state the page is left in after the stop, whether it errors when nothing is loading, or whether it is idempotent.

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 the primary behavior front-loaded, then the scope constraint, then the disambiguation. Nothing is repeated and no sentence is filler.

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, non-destructive, zero-required-parameter action with a fully documented schema and no output schema, the definition covers what the tool does and how it differs from its nearest sibling. Only minor edge-case behavior (no-op or error when not loading, resulting page state) is left unstated.

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 description coverage is 100% and both tabId and windowId are documented in the schema, including their defaulting behavior. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Stop the page loading in this tab') and anchors it with a concrete analogy to the browser's stop button, so the effect is unambiguous. It also explicitly separates itself from browser_stop_task, which an agent could otherwise confuse with it.

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?

Gives an explicit exclusion ('This is about page loading only') plus a named alternative and the condition that selects it ('To stop a running browser_run_task, use browser_stop_task'). This is exactly the when/when-not/alternative pattern an agent needs to route correctly among the many browser_* siblings.

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