delete_cookie

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

With no annotations provided, the description carries full burden. It correctly labels the tool as destructive (deletion), but does not disclose side effects like potential logout if all cookies are deleted, behavior on non-existent names, or whether deletion is scoped to the current domain. The description is minimal but not misleading.

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 action and includes both key behaviors in parallel structure, with no superfluous 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?

Given the tool's simplicity (one optional parameter, no output schema), the description covers the main functionality. However, it lacks information about return values (e.g., confirmation or count of deleted cookies) and edge cases like handling non-existent cookie names. It is adequate but not comprehensive.

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 input schema only defines 'name' as an optional string. The description adds critical meaning: omitting the parameter deletes all cookies, while providing it deletes only the named cookie. This clarifies the optional behavior beyond the schema, which shows 0% description 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 clearly states the action ('Delete') and the resource ('cookie'), distinguishing between deleting by specific name or all cookies when name is omitted. This differentiates from sibling tools like 'add_cookie' and 'get_cookies', though it does not explicitly contrast them.

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 basic usage guidelines: either specify a cookie name to delete one, or omit the name to delete all cookies. However, it offers no guidance on when not to use this tool, alternatives, or prerequisites (e.g., browser must be started, cookies must exist).

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