clash.optimize.dns

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

Explicitly declares read-only nature, no modifications, and describes output structure (versioned report with findings and proposedActions). Mentions limitation of recommendations based on structural evidence only.

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?

Single paragraph with clear statements: version, purpose, output, non-modification, and constraint. Efficient but could be slightly more structured.

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?

Fully explains the tool for a no-parameter, no-output-schema scenario. Covers purpose, behavior, output, and limitations, making it easy for an agent to decide to invoke it.

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?

No parameters exist, so the description does not need to explain parameters. Schema coverage is 100% (empty schema), and the description provides full context for the tool's function.

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 it is a read-only DNS configuration diagnosis tool, lists specific checks, and distinguishes from sibling tools like clash.optimize.rules or clash.optimize.proxy_groups.

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?

States it does not modify DNS configuration and describes its recommendations, but does not explicitly specify when to use it versus other optimization or runtime tools.

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