cookie_delete

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

The description indicates deletion (a destructive action) but does not disclose details such as whether cookies are deleted permanently, if domain scoping affects behavior, or any side effects like session termination. No annotations provided to supplement.

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, well-structured sentence that front-loads the action and resource. No unnecessary words.

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?

The description covers the basic purpose and optional parameter, but lacks detail on exact behavior, return values, and edge cases (e.g., no matching cookies). An output schema exists, so return format is not needed, but more context would help.

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 description explains the optional domain scoping, adding meaning beyond the schema. However, it does not specify name matching behavior (exact, case-sensitive, wildcard) or the effect of null domain, and the schema has 0% description coverage.

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 the resource 'cookies' with the condition 'matching name (optionally scoped to domain)', effectively distinguishing it from sibling tools like cookie_list, cookie_set, etc.

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 (e.g., cache_clear for all cookies) or when not to use it. The context is implied by the tool name and siblings.

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