cookies_clear

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

No annotations provided. The description states 'Drop all cookies' implying a destructive action, but lacks details on scope (e.g., all cookies in jar, session vs persistent), reversibility, or side effects. Baseline transparency is adequate but minimal.

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?

Single short sentence with no filler. Extremely concise and front-loaded. Every word is meaningful.

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 no parameters, no output schema, and no annotations, the description is minimal but sufficient for a simple one-action tool. However, for a destructive operation, more context on behavior and consequences would improve completeness.

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?

No parameters in schema (schema coverage 100%). With zero parameters, the description does not need to add parameter semantics. Baseline of 4 is appropriate as the condition is trivially satisfied.

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 'Drop all cookies from the jar.' uses a specific verb (Drop) and resource (cookies), clearly indicating the action of clearing all cookies. It distinguishes well from siblings like cookies_get and cookies_set.

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 explicit guidance on when to use this tool versus alternatives. While the purpose is implied (clear all cookies), there is no mention of when not to use it or comparison to related tools like cookies_get or cookies_set.

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