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

No annotations are provided, so the description carries the full burden, and it does substantial work: it explains activation timing (post-condition-match), both modes, and that kill_connection drops TCP with no HTTP response. It omits whether an existing chaos config is replaced, what permissions are needed, and what is returned on success.

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?

It is short and front-loaded: the scoping distinction comes first, then modes, with no filler sentences. The trailing mode enumeration slightly duplicates what the schema's enum descriptions already say.

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 an 8-parameter mutation tool with no annotations, no output schema, and full schema coverage, the description supplies the two missing pieces an agent needs: when the chaos actually fires and what each behavior does to the client connection. Nothing essential is absent.

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 100%, so the schema already documents every parameter including enum semantics for mode and behavior. The description's worked example ('name=agung', 30% kill) and mode summary add conceptual framing rather than new parameter-level meaning, which fits the baseline 3.

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 uses a specific verb+resource ('Configure Rule-level Chaos for a specific conditional rule inside a mock') and explicitly contrasts itself with Global Traffic Chaos, which is the sibling set_traffic_chaos. An agent can distinguish the two without opening either schema.

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?

It states the key selection condition clearly: rule-level chaos only activates after the rule's conditions match, unlike global chaos which intercepts all requests. It does not, however, name the sibling tools by name (set_traffic_chaos, clear_rule_chaos, get_rule_chaos_status), so the routing advice stops short of explicit alternatives.

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