tool_delete_all_cookies

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

No annotations exist, so the description must fully disclose behavioral traits. While 'delete all cookies' implies a destructive action, it fails to warn about irreversible data loss, impact on session state, or the fact that cookies are cleared from the current browser context. This lack of transparency for a mutation tool is a significant gap.

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 conveys the tool's purpose without extraneous words. Every word earns its place, and the structure is front-loaded with the action and target.

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 (no parameters, no output schema), the description is largely sufficient. It tells the agent what the tool does. However, it could briefly note the side effect (e.g., 'aliases session') or usage scenario, but overall it is complete enough for a trivial 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?

With zero parameters, the schema provides no constraints. The description adds no parameter-specific meaning, but nothing is needed. The baseline score of 4 applies because there are no parameters to document, and the description adequately states the tool's function without needing to elaborate on inputs.

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 all cookies' clearly states the action (delete) and the resource (all cookies). It distinguishes itself from sibling tools like tool_delete_cookie (specific cookie) and tool_get_cookies (retrieval), making the purpose unambiguous.

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 guidance on when to use this tool versus alternatives like tool_delete_cookie or tool_get_cookies. The description does not mention prerequisites, context, or situations where clearing all cookies is appropriate, leaving the agent without decision support.

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