browser_cookie_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds that it lists all cookies optionally filtered, but does not disclose any additional behavioral traits (e.g., performance impact, pagination, or data freshness). With annotations covering the core safety profile, the description offers minimal extra value.

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 sentence that is perfectly front-loaded with the main action ('List all cookies') and conditional filtering. Every word earns its place; there is zero redundancy or filler.

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 absence of an output schema, the description fails to explain what the tool returns (e.g., list of cookie objects, details included). With only 2 optional parameters and no mention of return format or pagination, the description is incomplete for an agent to fully understand the context of the response.

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?

Schema description coverage is 100%—both parameters (domain and path) have descriptions in the schema. The description merely restates that filtering is optional, adding no new meaning beyond what the schema already provides. Baseline 3 is appropriate for full schema 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 explicitly states 'List all cookies' with optional filtering by domain/path, providing a clear verb+resource combination. It distinguishes this tool from siblings like 'browser_cookie_get' (single cookie retrieval) and 'browser_cookie_delete' (deletion) by specifying the listing action and optional filters.

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 implies usage for listing cookies but does not provide explicit guidance on when to use this tool versus alternatives like 'browser_cookie_get' or 'browser_cookie_delete'. No exclusions or contextual cues are given, leaving the agent to infer based on tool names alone.

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