Toggle Pppoe Server

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

No annotations are provided, so the description carries the full behavioral burden. It conveys only that the operation mutates state; it does not say whether enabling/disabling drops existing sessions, whether the change persists across reboot, what permissions are needed, or what happens when the value already matches the current state.

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?

A single front-loaded clause with no filler or repetition. It is efficient, though the extreme brevity is under-specification rather than disciplined conciseness.

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, so return values need not be explained. But for an annotation-free state-mutating tool that governs a service with dependent objects (accounts, online users), the definition omits side effects, prerequisites, and scope, leaving the agent without enough context to invoke it safely.

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 coverage is 0% and the single 'enabled' boolean has no schema description. The description does implicitly define the parameter's meaning (true = enable, false = disable), which is the only semantic needed for a boolean, but it adds no format, default, or required-ness detail.

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?

States a specific action pair (enable/disable) and a specific resource (PPPoE server), so an agent can immediately tell it apart from get_pppoe_server_config (read) and toggle_vpn_server (different resource). It stops short of explicitly naming those siblings, but the verb+resource pair is unambiguous.

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 says nothing about when to use this versus get_pppoe_server_config or the VPN toggles, nor does it state prerequisites such as existing PPPoE accounts or config. Usage must be inferred entirely from the name.

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