network_loss

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

No annotations are available, and the description only states the action without disclosing behavioral traits such as reversibility, side effects on pods, required permissions, or what happens to existing network connections. The default values in the schema hint at behavior, but the description itself adds no transparency.

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 a single sentence with no unnecessary words, but it is too minimal. While concise, it sacrifices completeness; however, the sentence does convey the core purpose efficiently.

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 complexity (chaos engineering, destructive action, 7 parameters, no output schema), the description is severely incomplete. It lacks information on what the tool returns, how faults are cleaned up, prerequisites, and any side effects. With no supplementary annotations, the agent has insufficient context to use the tool correctly.

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%, and the description does not explain any of the 7 parameters. Key parameters like 'selector_value', 'loss_percent', 'duration', and 'correlation' are left undefined, forcing the agent to rely solely on parameter names which may be ambiguous without 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's purpose: injecting packet loss faults into pods matched by a label selector. It includes the verb 'inject', the resource 'Pod through label selector', and the specific fault type 'packet loss'. This distinguishes it from sibling tools like network_delay (delay) and pod_kill (kill).

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention use cases, prerequisites, or scenarios where other tools (e.g., network_delay, network_external_delay) would be more appropriate.

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