winops_net_diag

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description adds that it flushes DNS cache (a state-changing action) and returns ipconfig output. It doesn't disclose potential side effects like clearing cached DNS entries or requiring admin privileges, but it does add some behavioral context beyond annotations.

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 concise with a clear return format and an example. It's front-loaded with the main action and includes a structured JSON return format. The example is minimal but sufficient. No wasted 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?

Given the tool has no parameters and a simple action, the description is fairly complete. It specifies the return format and includes an example. However, it could mention prerequisites like admin rights or the fact that flushing DNS may require elevation, but overall it's adequate for a simple tool.

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, and the schema coverage is 100% (empty properties). The description adds the return format and example, which is useful for understanding the output. Since there are no parameters, the description doesn't need to explain parameter semantics, but it does provide the return structure.

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 flushes the DNS cache and returns full ipconfig output, which is a specific verb+resource combination. It distinguishes from siblings like winops_net_firewall_list or winops_sys_info, though it doesn't explicitly name alternatives.

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 implies usage for DNS troubleshooting or network diagnostics, but it doesn't explicitly state when to use this tool versus alternatives like winops_sys_test_port or winops_net_firewall_list. The context is clear but exclusions are not provided.

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