stop

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

The annotations already flag destructiveHint=true, so the destructive nature is known. The description adds a small amount of context by specifying the affected target, the browser session, but does not disclose other behavioral consequences such as whether page state is lost or whether the stop is reversible.

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 description is a single, direct sentence with no filler or redundancy. It is concise and gets straight to the point, though the brevity leaves other dimensions underspecified.

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?

The description is too terse to be fully complete for a state-changing operation. It does not explain what 'stop' implies for the browser session, nor how it differs from close-oriented siblings, and it relies entirely on the annotations and schema for context.

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 the input schema already fully explains the optional 'lease' and 'session' parameters, including guidance about unique names for multi-agent environments. The description itself adds no additional parameter detail, so it earns the schema-covered baseline.

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 names a clear action, 'Stop', and a specific resource, 'browser session', so an agent can understand the basic operation. It does not distinguish it from siblings like session_close or session_close_all, but for a simple top-level stop command it is sufficiently clear.

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?

The description provides no guidance about when to use this tool versus sibling tools like session_close, session_close_all, or clean. It does not mention whether 'stop' is the right choice for ending the entire browser versus closing a tab or session, so an agent has to infer the usage.

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