Clear Browser Cookies

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context: 'clearing cookies can sign out accounts and irreversibly remove session state from the active context.' This goes beyond annotations and helps the agent understand the impact.

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 three sentences, each serving a distinct purpose: use case, preconditions/next step, and sensitivity. It is front-loaded and concise, though it could be more structured by explicitly listing parameters.

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 complexity (5 parameters, destructive, no schema descriptions), the description is incomplete. It does not explain parameter roles or how filter combinations affect behavior. The output schema exists, so return values don't need explanation, but the lack of parameter guidance leaves gaps.

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?

With 0% schema description coverage, the description must explain parameters. It mentions 'filters should be as narrow as possible' but does not explain the name, path, or domain parameters. It states acknowledgeRawCapture and acknowledgeCredentialAccess are required but omits what they mean or why they're needed. This is insufficient.

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 clearly states the use case: 'Use when a full-profile test needs a deliberate logged-out or clean-cookie state.' It specifies the verb (clear) and resource (browser cookies), and distinguishes from siblings like browser_get_cookies by focusing on the destructive action.

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 explicit when-to-use guidance ('Use when...'), preconditions ('acknowledgeRawCapture: true and acknowledgeCredentialAccess: true are required'), and a next step ('reproduce the intended authentication or redirect behavior after clearing'). It also advises narrowing filters.

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