List Pppoe Accounts

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

readOnlyHint=true already tells the agent this is a safe read, so the annotation carries the behavioral load. The description adds nothing beyond it: no note on whether results are paginated, whether disabled/unbound accounts are included, or what the listing reflects.

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?

It is a single phrase with no padding, but it is under-specified rather than concise. One short sentence cannot be considered appropriately sized for a tool that competes with a near-identical sibling.

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?

An output schema exists and there are no parameters, so the description need not explain return values. It is minimally complete for invocation, but it omits the one piece of context that matters here — how this differs from list_pppoe_online_users.

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 takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate, and the schema (additionalProperties: false, empty properties) is unambiguous on its own.

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?

"列出 PPPoE 账号" is a literal restatement of the tool name list_pppoe_accounts, so it adds no distinguishing information. It does not separate configured PPPoE accounts from the sibling list_pppoe_online_users, which is the one ambiguity an agent would actually need resolved here.

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 when-to-use guidance, no mention of alternatives (list_pppoe_online_users, add_pppoe_account, delete_pppoe_account), and no prerequisites. The agent must infer scope entirely from the tool name.

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