set_tun

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

With no annotations, the description carries the full disclosure burden. It adds a genuinely useful side-effect warning (Verge may restore its UI settings after a subscription reload), which is behavioral context beyond the schema. However, it omits permissions required, reversibility, and any indication of the response, so it only partially compensates for the absence of annotations.

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?

Two short sentences, front-loaded with the action and followed by the caveat. No filler, though it is terse to the point of omitting useful detail.

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 single-boolean toggle with no output schema and no annotations, the definition covers the core action and one important caveat, which is minimally adequate. It leaves gaps around the parameter's meaning and operational prerequisites.

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?

There is one boolean parameter (enable) with 0% schema description coverage. The word '开关' (toggle/switch) implies on/off semantics for the boolean, providing marginal information, but the description never names or explains the enable parameter or what true/false means.

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 verb (toggle/switch) and resource (TUN virtual network adapter mode), which is concrete enough for an agent to know exactly what changes. It does not explicitly contrast itself with similar siblings like set_mode or toggle_system_proxy, but the TUN-specific resource makes it distinguishable.

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?

No guidance on when to enable vs disable TUN, nor when to prefer this over set_mode or toggle_system_proxy. The cautionary note implies a usage caveat but does not function as when/when-not guidance.

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