network_external_delay

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

With no annotations, the description must fully disclose behavioral traits. It mentions creating a workflow and injecting delay, but does not explain safety profile, required permissions, side effects, or how to revert. Critical gaps for a chaos experiment tool.

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?

Single sentence is concise and front-loaded with the core action. However, for a complex chaos tool, a slightly longer description with structural hints would be more helpful without losing conciseness.

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?

With no output schema, no annotations, and 6 parameters (3 required), the description is incomplete. It does not explain workflow behavior, return values, error scenarios, or lifecycle management, leaving significant gaps for correct tool 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?

Given 0% schema parameter descriptions, the description adds context (e.g., external_url refers to third-party domains, duration/delay/deadline are time parameters), but does not detail each parameter's purpose or constraints. Only moderate additional meaning.

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?

Description clearly states the tool creates a ChaosMesh workflow to inject response delay into outgoing traffic to third-party domain names, specifying the action, resource, and target scope. It distinguishes from siblings like network_delay and httpchaos_delay by focusing on external third-party domains.

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 on when to use this tool versus alternatives (e.g., network_delay for internal traffic, httpchaos_delay for HTTP-specific delays). No when-not-to-use or prerequisite conditions provided.

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