clash.verge.preferences.set_basic

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

With no annotations, description thoroughly covers mutation behavior: two-phase commit (preview returns diff, confirm=true applies), authentication and capability requirements, validation against real enums, platform-specific unsupported feature (tray_event on Linux), and immediate effect of env_type. Could mention idempotency or partial updates.

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?

Well-structured with purpose first, then preview/confirm, authentication, validation, platform notes. Dense but each sentence serves a purpose. Minor redundancy like 'v1.1-C:' prefix could be removed.

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?

Covers major aspects: what it modifies, how to apply, authentication, validation, platform specifics. Lacks description of the diff structure output and failure behavior of ownerFingerprint. Good differentiation from sibling tools by specifying 'basic preferences'.

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%, but description adds value by listing all fields and providing context (validated against real enums, platform restrictions, immediate effect, ownerFingerprint for drift detection). Enhances understanding beyond schema descriptions.

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?

Clearly states verb 'Modify' and resource 'Clash Verge Basic UI preferences' with explicit list of fields (language, theme_mode, tray_event, env_type, start_page). Differentiated from sibling tools like configure_theme and configure_layout.

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?

Describes preview mode vs confirm mode, tray_event limitation on Linux, and immediate effect of env_type. However, lacks explicit guidance on when to use set_basic versus the more specific preference tools (configure_theme, etc.).

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