clash.verge.set_auto_close_connection

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

Discloses side effects: updates memory and verge.yaml, emits GUI refresh, verifies both states, and requires confirmation. Given no annotations, this covers behavioral traits well, though it does not mention failure scenarios.

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?

Three sentences: first for main action, second for side effects, third for requirement. Front-loaded, no fluff, every sentence earns its place.

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?

Given no output schema or annotations, the description provides good context on effects and confirmation. Lacks return value or error details, but adequate for a simple toggle with side effects.

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 100%, so baseline is 3. Description adds no new meaning beyond schema; 'light confirmation required' hints at confirmed parameter but doesn't elaborate.

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?

Description clearly states the tool enables or disables auto-close connection. The verb and resource are specific, but it does not explicitly differentiate from sibling set_* tools like set_ipv6, though the distinct resource makes it clear.

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?

Description mentions 'light confirmation required' but provides no explicit guidance on when to use this tool versus alternatives. No exclusions or context for when not to use.

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