Get Ipsec Client Config

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

The readOnlyHint=true annotation already establishes that this is a safe read, and the description adds nothing on top of it — no mention of auth/permission needs, whether the config includes secrets (pre-shared keys), or fallback behavior when no IPSec client is configured. It carries no behavioral information beyond the annotation.

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 short clause with no padding, so it is not verbose. But the clause merely duplicates the title, so it does not 'earn its place' — the agent gains nothing from reading it that the tool name did not already convey.

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?

For a zero-parameter read tool with an output schema and readOnlyHint, a minimal description is nearly sufficient — return values need not be explained. Still, the description is written only in Chinese while every sibling tool is named and described in English, and it gives no hint of what the config covers, leaving a small but real 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 takes zero parameters, so there is no parameter semantics burden on the description; the schema coverage is reported at 100%. Baseline 4 applies for a parameterless tool.

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 verb+resource ('获取 IPSec VPN 客户端配置'), which is enough to tell it apart from the PPTP/L2TP/OpenVPN/WireGuard siblings. However, it is a verbatim translation of the title 'Get Ipsec Client Config' and adds no distinguishing detail (e.g., which IPSec mode, client-side vs server-side) beyond the name itself.

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 versus alternatives such as list_vpn_clients, get_ike_server_config, or the other get_*_client_config tools. The description implies a read but offers no context, prerequisites, or exclusions.

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