ruyi_capture_wait

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

With no annotations, the description carries the full burden. It discloses two meaningful behaviors: default returns full request/response bodies, and internally drains via single-packet RPC to avoid overwhelming the bridge. However, it does not describe error handling or timeout behavior 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 two sentences, front-loaded with the purpose, and every sentence adds value. No fluff or repetition.

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 no output schema and no annotations, the description covers the essential context: what it does, when to use it, what to expect (full bodies), and a performance rationale. It does not explain return structure in detail, but for a retrieval-after-start tool, this is reasonably complete.

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 coverage is 75% (3 of 4 params described). The description adds some context by explaining that full bodies are returned by default, which aligns with maxBodyChars=0, and the internal drain mechanism hints at count/pageIdx behavior. However, pageIdx remains undocumented in both schema and description, so the description doesn't fully compensate.

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 '等待并获取抓包结果' (wait and get capture results), specifying the exact verb and resource. It also mentions it should be used after ruyi_capture_start, which distinguishes it from capture start/stop and intercept wait siblings.

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 states when to use: '在调用 ruyi_capture_start 后使用' (use after calling ruyi_capture_start). This provides clear context and sequencing, though it does not explicitly mention alternatives or exclusions.

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