httpchaos_delay

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

No annotations are provided, so the description must carry full behavioral burden. It only states that delay is injected, but does not disclose any side effects, destructive nature, authentication needs, rate limits, or what happens to traffic beyond delay. For a chaos tool, this is insufficient.

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 very concise: two sentences, no wasted words. The first sentence states the core function, and the second provides a clear alternative. It is front-loaded and efficient.

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?

The tool has 7 parameters with 0% schema description coverage and no output schema. The description only clarifies path and port, but leaves out explanation for required parameters like namespace and app, and does not describe the delay format, duration, or the effect on target (Request vs Response). This is incomplete for a chaos tool.

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%, so the description must compensate. It adds value by mentioning 'HTTP path and port', which clarifies the 'path' and 'port' parameters, and 'inject delay' hints at 'delay'. However, it does not explain the other parameters like 'namespace', 'app', 'target', 'duration', leaving gaps.

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 that the tool injects delay by HTTP path and port, precisely affecting a specified interface. It also explicitly distinguishes itself from the sibling tool network_delay, which is for overall network delay. This provides a specific verb+resource and differentiates among siblings.

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 gives explicit guidance: use this tool for precise path/port delay, and use network_delay for overall network delay. This is a clear context with an exclusion, though it does not address when to use it versus other sibling tools like network_loss or pod_kill.

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