Set Parallels network condition

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

The description discloses the behavioral effect (simulating degraded network or offline state) and how to reverse it ('off' restores normal). Annotations already mark destructiveHint=true, and the description adds that the change is reversible via 'off', which is valuable context beyond the 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 (two sentences plus a structured Args section). The purpose is front-loaded, and each line adds value—no filler or redundancy. The format is easy to scan and understand.

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?

For a simple two-parameter tool, the description covers purpose, parameters, and the disabling behavior. It doesn't detail return values, but an output schema exists (indicated by context), so that is not required. It could mention immediate impact on connectivity, but that is not essential for correct invocation.

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 description coverage is 0%, but the description compensates fully. It explains 'vm' as the VM name or UUID and lists all valid 'profile' values with the special meaning of 'off'. This is far more than the schema provides, which only shows types and default.

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's action: 'Simulate degraded network conditions or offline state for the VM.' It identifies the resource (VM) and the specific effect (network degradation or offline). It is distinct from sibling tools, none of which mention network manipulation, so purpose is unambiguous.

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 provides clear usage context: it simulates degraded network conditions and explicitly explains how to disable simulation using 'off' to restore normal conditions. While it doesn't name alternative tools or state when not to use it, the tool's unique purpose and the parameter guidance make usage clear.

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