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

No annotations are provided, so the description carries the full burden; "Read" does establish it is non-mutating, and "Token-efficient" hints at response size. It says nothing about permissions, behavior when no chaos is configured, or error cases for invalid rule IDs — gaps for a tool with zero annotation coverage.

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?

Three short sentences, front-loaded with the verb+resource and followed by the alternative. Every sentence carries information, though the 'token-efficient counterpart' clause sits slightly awkwardly after the routing advice.

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 three-required-parameter read with fully documented parameters and no output schema, the description covers what the tool returns conceptually (one rule's chaosConfig) and when to prefer it. The absence of any note on the shape of a 'no chaos configured' response is the only real gap.

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% and the ruleId field already documents the crucial stale-ID caveat after update_mock, so the schema does the heavy lifting. The description adds no parameter meaning beyond what the schema provides; baseline 3 applies.

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?

"Read the current Rule-level Chaos configuration for a specific rule" states a precise verb (read) and a narrowly scoped resource (one rule's chaosConfig). It is immediately distinguishable from set_rule_chaos, clear_rule_chaos and get_mock_detail.

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?

Explicitly says "Call this instead of get_mock_detail when you just need to check one rule's chaosConfig" and positions itself as the counterpart to get_traffic_chaos_status, giving a clear selection rule. It does not state exclusions (e.g. when the whole mock is actually needed), so it falls just short of a 5.

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