cookie_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does reveal the important destructive condition 'Both empty = clear all', but it does not state that deletion is irreversible, how name and domain narrowing works, or whether clearing cookies affects all tabs or only the current context. This leaves significant behavior unexplained for a destructive tool.

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 extremely short and front-loaded: the core action comes first, followed by the critical clearing condition. Both sentences earn their place and there is no filler. It sacrifices completeness for brevity, which is appropriate given the tool's simplicity.

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 destructive tool with no annotations and no output schema, the description is incomplete. It does not clarify how to target a single cookie, what the exact matching behavior is, or what happens when only one parameter is provided. An agent can invoke it safely only for the 'clear all' case; targeted deletion remains ambiguous.

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 description coverage is 0%, so the description must explain the two parameters. It only explains the case where both are empty; it never explains what happens when name is set, domain is set, or both are set. The agent is left to guess the matching semantics for a specific cookie deletion.

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 states a clear verb and resource: 'Delete cookies'. It also adds the key scope detail that leaving both parameters empty clears all cookies, which distinguishes it from cookie_set, cookie_list, and cookie_export. It does not differentiate sibling delete-like tools because there are none, so clarity is high but not maximum.

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?

There is no guidance on when to use this tool versus alternatives. The only contextual hint is 'Both empty = clear all', which describes invocation behavior rather than the situations where deletion is appropriate. It does not mention conflicts with cookie_set, cookie_export, or session storage tools.

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