browser_clear_cookies

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

No annotations are provided, and the description does not disclose behavioral traits like scope of cookie clearing (all cookies vs. specific ones), side effects (e.g., logging out user), or persistence. The minimal description fails to communicate important behavioral information.

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 sentence that is concise and front-loaded with purpose. However, it is too brief to cover essential details, but as a concise statement it earns its place.

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?

Despite low complexity and an output schema, the description lacks completeness: it does not mention return values, when to use, or effect on browser state. The single sentence fails to provide enough context for reliable tool invocation.

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 input schema has one parameter 'session_id' with 0% description coverage, meaning neither schema nor description explains its role. The description provides no parameter information, leaving the agent uninformed about what session_id signifies.

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 'Clear browser cookies.' uses a specific verb and resource, clearly indicating the tool's action and target. It effectively distinguishes from sibling tools like 'browser_get_cookies' and 'browser_set_cookies.'

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 cookies for session reset or privacy reasons. No exclusions or context are given.

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