ruyi_list_network_requests

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

The description mentions it is based on the performance API, implying a read-only, non-intrusive operation, but does not explicitly disclose non-destructive behavior or limitations (e.g., no request bodies or timing details). With no annotations, more behavioral context could be expected, but this adds some 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?

Two concise sentences, front-loaded with the primary purpose, followed by a clear alternative. Every sentence contributes value without redundancy.

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?

The tool is relatively simple with no required parameters. The description clarifies the data source (performance API) and directs users to a more detailed alternative. While it does not explain pagination or return format, the output schema absence makes some additional info helpful, but the essential context is provided.

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 covers limit and urlFilter with descriptions (67% coverage), and the description does not add extra meaning for parameters. pageIdx lacks description, and this description does not compensate, so baseline 3 is appropriate.

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 '列出最近的网络请求' (list recent network requests) with a specific verb and resource. It also distinguishes itself from alternatives by suggesting ruyi_capture_start for more detailed information, aligning with the sibling context.

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?

Explicitly indicates when to use this tool for basic resource loading info and when to use ruyi_capture_start instead ('需要更详细信息时'). This provides clear usage context and an alternative, fulfilling the when/when-not guidance.

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