Delete a specific browser cookie by name, optionally narrowing by domain or path, to clear session data and reset browser state.
Delete cookies by name, optionally narrowed by domain/path.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Cookie name to delete. | |
| path | No | ||
| domain | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only says 'Delete cookies' without noting that this is destructive, irreversible, or what happens if the cookie does not exist. Lacks any side-effect or error context.
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 concise sentence that front-loads the core action and mentions the optional parameters. No wasted words, though it could be slightly more informative without losing 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?
For a mutation tool with no annotations and no output schema, the description is under-specified. It does not mention return behavior, success/failure indications, or distinguish itself from browser_cookie_clear. The agent has no guidance on prerequisites or consequences.
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 only 33% (name has a description; path and domain do not). The description adds 'optionally narrowed by domain/path' but does not clarify the expected format or semantics of path/domain, leaving the agent to guess. Minimal value added beyond the schema.
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 action ('Delete cookies') and the primary resource ('by name'), with optional narrowing by domain/path. This distinguishes it from other cookie tools like get or set, though it does not explicitly contrast with the sibling 'cookie_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?
No guidance on when to use this tool versus alternatives such as browser_cookie_clear or browser_cookie_set. The description implies it is for targeted deletion but does not state conditions or when to prefer it over clearing all cookies.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.