Clear Browser Cookies

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, so the description adds little beyond confirming the action. It does specify 'active browser context' as scope, but no additional behavioral traits like irreversibility or side effects are disclosed.

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, front-loaded sentence with no filler or redundancy. It contains exactly the necessary information for a simple parameterless destructive action.

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 tool is simple with no parameters and an output schema indicating return-value documentation is not needed. The description fully conveys the action and scope. It could add a note on irreversibility, but annotations already flag destructive behavior.

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 has zero parameters, and the base score for parameter-less tools is 4. The description adds no parameter details, but none are needed, and the schema confirms no parameters.

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 ('all cookies') with explicit scope ('active browser context'). It clearly distinguishes from sibling tool browser_cookies_delete by specifying 'all cookies' rather than a subset.

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 phrase 'Clear all cookies' implies this is for a full cookie reset, but there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives like browser_cookies_delete for targeted removal. The usage context is only lightly implied.

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