browser_set_cookies

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

No annotations are present, so the description carries the full burden. It only says 'Set Cookie' and does not disclose behavioral details such as whether existing cookies are overwritten, whether a page must be active, or any side effects. For a mutation tool, this is insufficient.

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 extremely short (two characters in Chinese), which is under-specification rather than efficient conciseness. It conveys the basic idea but lacks structure and necessary detail, making it unhelpful for an agent.

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?

This tool has no output schema, no annotations, and a single parameter. The description is too sparse to provide complete context. It does not explain the format of cookies, expected behavior, or any prerequisites, making it inadequate for reliable 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?

The input schema lists a single 'cookies' array with no description. The tool description does not explain the expected structure of array elements (e.g., name, value, domain, path). With 0% schema coverage, the description fails to compensate, leaving the parameters entirely ambiguous.

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 states '设置Cookie' (Set Cookie), which is a specific verb and resource, clearly indicating that the tool sets cookies. This distinguishes it from sibling tools like browser_get_cookies and browser_clear_cookies. However, it does not elaborate on the exact scope (e.g., for the current page, all pages), so it slightly lacks precision.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions. It is a bare statement without any usage direction.

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