delete_all_cookies

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete all' clearly signals a destructive mutation, it does not disclose consequences such as invalidating authentication, irreversibility, or whether other sessions or browsing contexts are affected. It also says nothing about return behavior.

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, tight sentence with no filler. The action verb and object are front-loaded, and every word contributes to the meaning.

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 zero-parameter destructive action, the description is minimally sufficient but omits side-effect warnings and any indication of post-deletion behavior such as session invalidation or return value. No annotations or output schema exist to fill those gaps, so completeness is moderate.

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 tool accepts zero parameters and has 100% schema coverage, so there is no parameter documentation burden on the description. The 'current session' phrasing still adds useful scoping context beyond the empty schema.

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 verb 'Delete' and precisely scopes the action to 'all cookies' in the 'current session.' This distinguishes it from sibling delete_cookie, which targets a single cookie, and from read-only cookie tools like get_cookies.

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 the context of clearing the entire cookie set for the current session, but it does not explicitly contrast this with delete_cookie or state when to use one over the other. The differentiation is left to inference from the tool name and sibling list.

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