list_pppoe_accounts

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

With readOnlyHint=true, the annotation covers the safety profile, but the description adds no extra value. It fails to clarify whether 'PPPoE accounts' means configured accounts or active sessions, which is a meaningful behavioral trait given the existence of list_pppoe_online_users. No additional context about response format or filtering is provided.

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 phrase '列出 PPPoE 账号' that immediately conveys the purpose. It is appropriately sized for a tool with no parameters and simple functionality, with no wasted words.

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 and has an output schema, but the description lacks a crucial distinction between accounts and online users. Without stating that this lists configured PPPoE accounts (as opposed to current sessions), it is not fully complete for disambiguating from list_pppoe_online_users. The minimal text is functional but leaves a subtle gap.

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 tool has zero parameters, so the description has no duty to explain parameter semantics. The baseline of 4 applies because the empty schema fully documents the parameter requirements and there is nothing for the description to add.

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 action (list) and resource (PPPoE accounts), distinguishing it from sibling tools like list_pppoe_online_users. It is specific and unambiguous about the core operation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention the distinction from list_pppoe_online_users or specify that it returns configured accounts rather than online sessions. Usage is only implied by the tool name, not the description.

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