ruyi_delete_cookies

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

The description discloses that omitting the 'name' parameter clears all cookies, which is a significant behavioral trait. However, with no annotations provided, the description carries the full burden and does not mention other important details such as whether cookies are cleared only for the current site or all domains, or whether the action is reversible. It adds some context but not comprehensive transparency.

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 direct and front-loaded. It conveys the essential behavior without unnecessary 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 simple cookie deletion tool with no output schema and no annotations, the description covers the main behavior and default case. However, it could be more complete by noting the destructive nature or scope of the deletion. It is adequate but not exhaustive.

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 already provides descriptions for both parameters with 100% coverage. The description restates the 'name' parameter's default behavior ('不传则清除全部') without adding new meaning. The pageIdx parameter is not mentioned in the description, though the schema describes it as a tab index.

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 the tool deletes cookies, with a specific verb and resource. It mentions the default behavior of clearing all cookies when no name is provided. However, it does not explicitly differentiate from sibling tools like ruyi_clear_site_data or ruyi_set_cookies, so it lacks explicit sibling differentiation.

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?

There is no guidance on when to use this tool compared to alternatives such as ruyi_clear_site_data or ruyi_set_cookies. The description only explains the basic operation and default behavior, without stating prerequisites or when not to use it.

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