proxychains_dns

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

With no annotations, the description carries full burden. It explains each mode's behavior (e.g., 'DNS through proxy'), but lacks details like persistence, scope, or side effects. This is adequate for a simple configuration tool.

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 extremely concise, with a short lead sentence and a single line for each mode. No extraneous words, every sentence adds value.

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 simplicity (one parameter, no output schema), the description covers all modes and offers a recommendation. It lacks details on return values or if changes persist, but these are not critical for a DNS mode setter.

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%, and description adds clarity by explaining the meaning of each enum value beyond the schema's bare list (e.g., 'proxy_dns (recommended)'). This provides actionable context.

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 configures DNS handling, providing a specific verb-resource pair. It lists distinct modes, distinguishing it from sibling tools like run or config.

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?

Description recommends 'proxy_dns' mode and explains each option, offering implicit guidance. However, it does not explicitly state when not to use this tool or compare with siblings beyond listing modes.

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