cookie_delete

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

With no annotations, the description carries the full behavioral burden for a destructive operation. It conveys scope (one cookie vs. all cookies of a site) but says nothing about irreversibility, required permissions, or what happens when the site/cookie is not found.

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?

A single front-loaded sentence with no filler, which is efficient for a simple tool. It borders on under-specification rather than wasting words, so full marks are not warranted.

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 simple cookie-removal tool with no output schema and no annotations, the description covers the action but omits how the target is identified and the safety profile of an irreversible delete. Adequate but with visible gaps for a destructive operation.

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 declares zero parameters, which per the baseline would warrant a 4. However, the description promises two distinct targeting modes ("one cookie" or "every cookie of one site") that the empty schema provides no way to express, leaving the agent with no documented mechanism for selecting a cookie or site.

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 gives a specific verb ("Remove") and resource ("cookie") plus a clear scope: a single cookie or all cookies of one site. It is unambiguous about what the tool does, but it never names or contrasts with the obvious sibling cookie_list.

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 explicit guidance on when to use this versus cookie_list, nor any mention of prerequisites, confirmation requirements, or when deletion is inappropriate. The two deletion modes are stated but not framed as a choice the agent must make.

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