browser_clear_cookies

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only says 'Clear all cookies' and fails to mention the impact on the browser session, whether it clears cookies for a specific sessionId or globally, or if it persists across navigations. This is a significant gap for a mutation tool.

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 extremely concise with no wasted words, but it is under-specified. While it is front-loaded and clear, it omits critical parameters and behavioral details, making it borderline acceptable for conciseness.

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?

Given the tool's complexity (one optional parameter, no output schema), the description is incomplete. It does not explain how the optional sessionId is used, what the return value (if any) is, or what side effects clearing all cookies has on the browsing context. This leaves the agent with insufficient information to use the tool correctly in varied scenarios.

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% because the sessionId parameter has a description ('Browser session ID'), so the baseline is 3. The tool description does not add any further meaning about how sessionId affects the clearing operation, but it doesn't need to because the schema already provides basic parameter semantics.

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 uses a specific verb 'clear' and resource 'cookies' with scope 'all', clearly distinguishing it from sibling tools like browser_get_cookies and browser_set_cookies. It leaves no ambiguity about the tool's primary function.

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 on when to use this tool versus alternatives, such as when to clear specific cookies via browser_set_cookies or whether it should be used before navigation. It simply states the action without contextual or conditional advice.

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