Get Pppoe Server Config

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

The readOnlyHint=true annotation already declares the safe-read nature of the call, and the description adds nothing beyond that - no mention of what the config covers, whether it requires prior enablement of the PPPoE server, or any caveats. It does not contradict the annotations, but it contributes no behavioral context of its own.

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 short phrase, so it is not bloated, but the brevity comes from under-specification rather than economy: the sentence merely echoes the name and earns little place of its own.

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 zero parameters, an output schema present (so return values need not be explained), and readOnlyHint covering the safety profile, the definition is functionally callable. However, it omits any distinguishing detail from its many server-config siblings, leaving a real gap for tool selection.

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 the schema carries no parameter semantics to document; per the rubric this is the baseline 4. The description correctly implies a no-argument getter, though it adds no extra meaning.

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 direct restatement of the tool name get_pppoe_server_config; it is essentially a tautology of the title rather than an elaborated statement of purpose. It gives no differentiation from near-identical siblings such as get_pptp_server_config, get_l2tp_server_config, or get_openvpn_server_config.

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 prerequisites, and no pointer to alternatives. An agent cannot infer from the description when this config getter is the right choice versus the many other *_server_config getters.

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