cookies_clearClears cookies for the domain of the active tab, or a specific tab if provided.
清除标签页所属域的 cookies。
| Name | Required | Description | Default |
|---|---|---|---|
| tab_id | No | 标签页 id，省略时用最新标签页 |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| message | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The destructiveHint annotation already signals the destructive nature, and the description confirms it clears cookies; however, it does not disclose side effects such as clearing all cookies for the domain or affecting the current session.
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 with no unnecessary words.
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 description and schema together sufficiently cover the tool's purpose and parameter for a simple action, though the absence of an output schema leaves behavior unspecified.
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 schema fully describes the single tab_id parameter, including its default behavior, so the description adds no additional semantic value 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 tool's action: clearing cookies for the domain to which a tab belongs, distinguishing it from cookies_get and cookies_set.
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 conveys what the tool does but does not explicitly state when to use it versus alternatives, such as cookies_get or cookies_set.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.