clash.verge.get_directories

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

No annotations are provided. The description implies a read-only operation ('Get'), but does not explicitly state safety, idempotency, or any side effects. For a getter, the behavioral disclosure is adequate but minimal.

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 concise sentence that efficiently communicates the tool's purpose and output. Every word adds value with no redundancy or extraneous information.

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 lists the returned items sufficiently for a simple getter. However, it lacks detail on the output format (e.g., whether it is a string, object, or dictionary). With no output schema, a slightly more explicit structure would be helpful, but the description is largely complete.

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 tool has zero parameters. According to guidelines, 0 parameters defaults to a baseline of 4. The description correctly adds no parameter info as none exist.

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 tool retrieves Verge config directories and lists specific items (config root, profiles dir, executable path, unix socket). This is a specific verb-resource combination that distinguishes it from siblings, which deal with settings, profiles, runtime, etc.

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 implicitly indicates use when these directory paths are needed. No explicit exclusions or alternatives, but given its unique purpose among siblings (no other tool gets directories), the context is clear.

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