cookie_remove

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

The warning about clearing all cookies affecting the entire browser provides important behavioral context. However, it does not disclose how domain or tab_id parameters affect behavior (e.g., scoping), leaving ambiguity. No contradictions with annotations (none present).

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?

Two sentences with no extraneous information; the action and a critical warning are front-loaded. Could be slightly improved with structured bullets but is already concise.

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?

Despite having an output schema (not shown), the description is incomplete for a mutation tool. It fails to explain the role of domain and tab_id, and does not clarify if the removal is scoped or applies across all contexts, leaving significant gaps for correct invocation.

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?

Only the 'name' parameter is explained (null clears all). The 'domain' and 'tab_id' parameters are undocumented in the schema (0% coverage) and the description adds no meaning for them, leaving the agent unaware of their purpose or effect.

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?

Description clearly states the tool removes a cookie by name or clears all cookies if name is not provided. It differentiates two modes, but does not explicitly mention the domain or tab_id parameters.

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?

Usage is implied based on the action (remove specific cookie or clear all), but no explicit guidance on when to use this vs sibling tools like cookie_get_all or cookie_set, nor any conditions or prerequisites.

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