list_pppoe_online_users

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

The annotation readOnlyHint=true already indicates a safe read operation. The description adds the 'online' status which implies a live snapshot, but nothing else about pagination, rate limits, or data recency. Given the annotation coverage, this is acceptable but not rich.

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 clear sentence that is front-loaded and contains no filler. Every word is meaningful for a tool with no parameters.

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's simplicity (0 params, read-only, output schema present), the description is nearly complete for the operation. However, it could have noted that this lists only PPPoE online users, contrasting with list_pppoe_accounts for configured accounts, to improve context.

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?

There are zero parameters, and the schema has 100% coverage (vacuously). The baseline for 0 params is 4. No additional parameter semantics are needed, and the description does not need to 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 the tool lists current online accounts. The verb 'list' and resource 'online accounts' make the purpose specific. However, it does not explicitly distinguish from sibling tool list_pppoe_accounts, which lists configured (not necessarily online) accounts, so it misses an opportunity for differentiation.

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?

There is no guidance on when to use this tool versus alternatives. No context is given about when this is preferred over list_pppoe_accounts or how it relates to kick_pppoe_user for managing online users.

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