simulate_network_drop

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

With no annotations, the description carries the full burden. It discloses the core behavior (aborting requests after a delay) but omits the fallback verification feature (fallback_selector) and any potential side effects. This is a clear gap, as the schema indicates the tool can check for a fallback UI, which is an important behavioral trait.

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 two sentences, front-loaded with the core action and followed by a concrete use-case example. There is no redundant information or irrelevant filler.

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 description fails to mention the fallback checking behavior implied by fallback_selector and does not describe the overall workflow (load, drop, verify). With six parameters, no output schema, and no annotations, the description is too sparse to fully guide an agent on what the tool does end-to-end.

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?

The schema covers all parameters with descriptions (100% coverage), so the description doesn't need to repeat them. It adds minimal value beyond the schema, though the example scenario helps illustrate the purpose of intercept_pattern and drop_after_ms. Baseline 3 is appropriate given the schema coverage.

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 ('aborts') and resource ('requests matching a pattern') and clearly states the behavior in the first sentence. It is easily distinguished from sibling tools like inject_latency (delays only) and block_resources (blocks immediately) by describing a delayed mid-flight drop.

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 second sentence provides explicit context: 'Use to answer: what happens if the network drops after the order request is sent but before the response arrives?' This clearly indicates when the tool is appropriate, but it does not mention alternatives or when not to use it.

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