ruyi_get_cookies

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'get' clearly implies a read-only operation, the description does not elaborate on return format, whether cookies from all domains are included, or any edge cases. It adds minimal context beyond the action itself, but for a simple read operation this is adequate.

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, concise sentence in Chinese that fully captures the tool's purpose. It contains no superfluous information and is easy to parse quickly.

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 is a simple read-only tool with one optional parameter, and the description clearly states its function. There is no output schema, but 'get cookies' implicitly conveys the return value. The lack of information about return format or edge cases is acceptable given the low complexity and strong schema coverage.

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 schema description coverage is 100%, meaning the single parameter pageIdx is already documented as '标签页索引' (tab index). The tool description adds no additional parameter semantics. According to the rubric, a baseline of 3 is appropriate when schema covers all parameters and the description does not compensate further.

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 uses a specific verb ('获取' meaning 'get') and a clear resource ('当前页面的所有 cookies' meaning 'all cookies of the current page'). This clearly distinguishes it from sibling tools like ruyi_set_cookies and ruyi_delete_cookies, which perform different cookie operations.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios for cookie reading vs writing, nor does it reference related tools like ruyi_set_cookies, ruyi_delete_cookies, or ruyi_clear_site_data. There is no explicit usage context or exclusions.

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