clash.verge.set_unified_delay

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

With no annotations, the description carries the full burden. It discloses that 'light confirmation is required' and that the tool returns COMMITTED only after persistence, runtime, GUI-refresh, and five-state verification succeed. This gives good insight into the post-invocation behavior and side effects.

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?

The description is a single sentence that efficiently conveys the core action and key behavioral details. It is front-loaded with the verb and resource, and every clause adds value. However, it could be slightly restructured for readability.

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 the tool's low complexity (two boolean params, no output schema) and no annotations, the description covers the essential behavioral context: the need for confirmation, the verification steps, and the return condition. It adequately informs an agent about the tool's operation.

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 input schema fully describes both parameters (value and confirmed) with clear descriptions. The description adds 'Light confirmation required,' which reinforces the confirmed parameter but does not provide additional semantic value beyond the schema. With 100% schema coverage, a score of 3 is appropriate.

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 clearly states the verb 'Set' and the resource 'unified-delay', making the tool's purpose clear. It mentions 'authenticated native Clash Verge Adapter', which hints at its specific domain but does not explicitly differentiate it from sibling tools like 'set_ipv6' or 'set_log_level'.

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 implies the tool is used to set unified delay and mentions the requirement for confirmation and the conditions for returning COMMITTED. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor does it reference alternative tools for similar actions.

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