ruyi_set_cache_behavior

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

The description adds Chinese translations for the enum values (e.g., '跳过缓存' for bypass) but does not disclose side effects, persistence, whether it affects current or future navigations, or how pageIdx influences behavior. With no annotations, the description carries the full burden, and it fails to provide substantive behavioral context beyond the schema.

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 that front-loads the purpose. There is no redundancy, and the mode options are listed compactly. It could benefit from a structured breakdown, but it is efficient and to the point.

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 tool is a state-changing browser operation with no annotations or output schema, the description is incomplete. It omits pageIdx semantics, when to set cache behavior, interactions with cache-clearing tools, and whether the setting applies to the current page or future navigations. This is a significant gap for an agent to use the tool correctly.

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?

Schema description coverage is 50%; pageIdx has no description and the description does not mention it. The description glosses the mode enum values (default, bypass, force_cache) with Chinese meanings, adding some value, but it leaves pageIdx completely unexplained and fails to fully compensate for the schema's gaps.

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's function: '控制浏览器缓存行为' (control browser cache behavior), and lists the three modes. It is specific about the resource (browser cache) and action (control/set), distinguishing it from siblings by focusing on cache behavior rather than navigation or data clearing, though it doesn't explicitly differentiate.

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 like ruyi_clear_site_data or navigation tools. The description only lists the modes without context on which scenario each mode suits or prerequisites.

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