delete_cookie

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only states the action without explaining behavior when the cookie does not exist, whether deletion is scoped to the current domain/path, or any side effects beyond the obvious removal.

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 focused sentence that conveys the essential information with no filler. Every word contributes to understanding the tool's purpose.

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 one-parameter tool with no output schema, the description is arguably sufficient for basic invocation. However, the absence of annotations and any detail about error handling or cookie scoping leaves gaps that could matter in real browser automation contexts, so the definition is adequate but not rich.

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 provides only a string field named 'name' with no description, so the phrase 'by name' adds meaningful context by clarifying that the parameter refers to the cookie's name. However, it does not elaborate on format, required cookie scope, or special values, providing only minimal compensation for the 0% schema coverage.

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 action ('Delete') and resource ('a specific cookie'), with the selection criterion ('by name') that distinguishes it from delete_all_cookies. It does not explicitly name sibling tools, so it stops short of a fully explicit differentiation, but the purpose is unambiguous.

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 gives no guidance on when to use this tool versus alternatives like delete_all_cookies or set_cookie. The intended use is implied by the name and description, but no conditions, prerequisites, or exclusions are provided.

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