Delete Pppoe Account

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

No annotations are provided, so the description carries the full disclosure burden. 'Delete' implies a destructive mutation, but nothing is said about permanence, reversibility, whether the account must be offline first, permission requirements, or cascading effects (e.g., deleting associated credentials/sessions).

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 short phrase with no filler, so it is concise, but it is sized far below what a destructive, undocumented parameter tool warrants. It is front-loaded in the trivial sense that there is only one clause.

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?

With no annotations, 0% parameter coverage, and an output schema present (so return values need not be explained), the description is still missing key behavioral context for a destructive delete operation. An agent lacks the information needed to invoke it safely and correctly.

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 description coverage is 0% and the description provides no information about the single parameter user_id — not its format, source (e.g., from list_pppoe_accounts), or whether it accepts a username vs. an ID. It adds nothing beyond the schema's bare integer type.

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 states a specific verb+resource ('删除 PPPoE 账号' = delete PPPoE account), which is clear enough to tell apart from siblings like list_pppoe_accounts, add_pppoe_account, and kick_pppoe_user. However, it is essentially a verbatim restatement of the tool name/title and adds no scope, target, or distinguishing detail beyond that.

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 such as kick_pppoe_user (disconnect vs. delete) or delete_vpn_account. The agent must infer usage entirely from the tool name, with no conditions, prerequisites, or exclusions provided.

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