ruyi_set_cookies

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

Since no annotations exist, the description carries the full burden of behavioral disclosure. It states the input format but does not mention whether cookies are merged with or replace existing ones, whether the operation targets the page indicated by pageIdx, or any persistence/scope details.

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 two concise Chinese sentences, front-loaded with the core operation. It contains no redundant or filler content, and every sentence adds useful input-format detail.

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?

For a mutation tool with no annotations and no output schema, the description covers the input structure well but lacks behavioral context such as overwrite/merge semantics, tab targeting via pageIdx, and any side effects. It is minimally acceptable for a simple setter but has clear gaps.

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 explicitly requires 'name' and 'value' in each cookie object and enumerates optional fields (domain, path, secure, httpOnly, sameSite, expiry), going beyond the schema's abbreviated 'domain?, path?, ...'. While pageIdx is not mentioned in the description, the schema provides its meaning, maintaining adequate semantics.

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 opens with '设置 cookies' (set cookies), which is a specific verb+resource pair, and further explains the required cookie object array. This clearly distinguishes it from sibling tools like ruyi_get_cookies, ruyi_delete_cookies, and ruyi_clear_site_data.

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 about when to use this tool versus alternatives is provided. The intended usage is only implied by the tool's name and description; there is no mention of when not to use it or references to sibling cookie-related tools.

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