browser_delete_cookies

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

The description only states 'Delete', implying a destructive operation, but fails to disclose that deleting all cookies occurs when the 'name' parameter is empty. No annotations are provided, so the description should carry the full behavioral burden but does not cover session requirements, side effects, or irreversibility.

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 concise (3 words) but lacks structure. It conveys the core purpose efficiently but omits important details that could be included without significant verbosity.

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 presence of an output schema and full parameter documentation, the description is still incomplete. It does not address behavioral aspects like what happens after deletion, whether the action is reversible, or the need for a valid session. More context would improve agent decision-making.

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% for both parameters, providing clear meanings for 'session_id' and 'name'. The description adds no extra semantic value beyond the schema, achieving the baseline score.

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 browser cookies' clearly states the verb (delete) and resource (browser cookies), distinguishing it from sibling tools like browser_get_cookies and browser_set_cookie. However, it does not explicitly mention the optional cookie name filtering, which is covered in the schema.

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 on when to use this tool versus alternatives such as browser_set_cookie or browser_get_cookies. The description lacks context about prerequisites (e.g., an active browser session) or typical usage scenarios.

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