clash.verge.preferences.configure_layout

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

The description discloses immediate effects, preview mode returning a Diff, and the need for confirmation, which is transparent for a configuration tool with no annotations. It could detail error behavior but covers key traits.

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 brief yet comprehensive, front-loading the purpose and constraints, with no unnecessary words.

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?

The description covers parameter constraints, preview/apply flow, and capability requirements, compensating for the lack of output schema with a clear statement about the return value.

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?

With 100% schema coverage, the description adds value by explaining the menu_order constraint, immediate behavior, and output format, going beyond the schema's basic 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?

The description clearly states 'Modify Clash Verge Layout preferences' and lists specific fields, which distinguishes it from sibling tools like configure_theme and configure_hotkeys.

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 explains the preview vs apply mode and the required capability (settings.verge-preferences-write), providing clear usage context, though it does not explicitly mention when not to use it or contrast with alternatives.

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