list_proxy_dial_online

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation, and the description aligns with that. However, the description adds no extra behavioral context such as pagination, sorting, or limits. The presence of an output schema covers return structure, so a score of 3 is appropriate given minimal additional value.

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, efficient phrase with no extraneous information. Every word contributes to the meaning, and it is appropriately sized for a tool with no parameters and a clear purpose.

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 simple (no parameters) and has an output schema, so the description sufficiently explains its core purpose. However, it could briefly clarify what 'online' status entails or whether it returns the same fields as list_proxy_dial_accounts. Given the low complexity, the current description is nearly 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?

This tool has zero parameters, so parameter semantics are trivially satisfied. Baseline for 0 params is 4, and the description does not need to explain any parameter details. The schema is also fully covered.

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 lists online proxy-dial accounts, using the specific verb 'list' and a well-defined resource ('online accounts'). This distinguishes it from sibling tool list_proxy_dial_accounts, which likely lists all accounts, by adding the 'online' qualifier.

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 implies usage for viewing currently online proxy-dial accounts, but it provides no explicit guidance on when to choose this tool over alternatives like list_proxy_dial_accounts. The sibling names give context, but the description does not state any exclusions or alternative conditions.

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