browser_cookie_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is clear. The description adds no behavioral context beyond what the annotations provide (e.g., what happens if the cookie doesn't exist, side effects, or scope). It is consistent but does not enrich understanding.

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 sentence, front-loaded with the key action. It is appropriately concise with no wasted words, though it could include a bit more context without losing conciseness.

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 destructive tool with one parameter and no output schema, the description is minimal. It does not clarify return behavior, error handling, or how to differentiate this from browser_cookie_clear. The lack of usage guidelines and behavioral detail makes it incomplete for an agent to use effectively.

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 100%—the sole parameter 'name' is described as 'Cookie name to delete'. The description does not add any extra meaning or constraints beyond the schema, so it meets the baseline with no added value.

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 'Delete a specific cookie' uses a specific verb and resource, clearly distinguishing this tool from siblings like browser_cookie_clear (deletes all cookies) and browser_cookie_set (creates/updates). It leaves no ambiguity about what the tool does.

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?

No guidance is provided on when to use this tool versus alternatives such as browser_cookie_clear or browser_cookie_set. There are no preconditions, error scenarios, or contextual hints that help an agent decide between siblings.

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