wavexis_cookie_list

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds 'Side effects: None; reads cookie state from the browser session' and details the return format, providing useful context beyond annotations.

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?

Three sentences: purpose with filters, alternative tool, side effects and return format. All information is essential and front-loaded, no wasted 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?

Given the annotations and the simple nature of the tool, the description adequately covers its behavior, return format, and alternatives. Minor omission: does not explicitly state that a session must be open, but this is inferable from the required session_id.

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 mentions 'name, domain, and path filters' but does not cover the 'limit' or 'session_id' parameters. With schema description coverage at 0%, the description partially compensates but lacks complete parameter detail.

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 'List browser cookies' with optional filters, distinguishing it from the sibling 'wavexis_cookie_get' for a single cookie.

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?

Explicitly mentions when to use 'wavexis_cookie_get' instead, providing clear alternative guidance. However, it does not mention the prerequisite of an open session, though this is implied by the required session_id parameter.

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