fuzz_endpoint

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

With no annotations provided, the description carries the full burden and delivers it: it discloses high-volume concurrent request sending, baseline measurement, anomaly detection criteria, and the mandatory approval requirement. It also explains the replacement workflow and concurrency aggressiveness, giving the agent a clear model of side effects.

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 longer than average but well-organized into labeled sections (REQUIRES, PREREQUISITE, HOW IT WORKS, SETUP, Args), with a front-loaded summary. Every sentence adds useful setup, workflow, or parameter information that is not present in the schema, so the length is justified.

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 complex tool with five parameters, the description provides a complete workflow from prerequisite capture to final anomaly detection, plus setup examples and approval requirements. It appropriately references sibling tools like replay_flow and browser_go, and since an output schema exists, not detailing return values is acceptable.

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 has zero description coverage, so the description must compensate—and it does. Each of the five parameters is explained with defaults, usage expectations, and examples, including the crucial approved flag semantics and the requirement that flow_id contain target_pattern.

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 opens with 'Fuzz a captured HTTP request by injecting payloads and detecting anomalies,' giving a specific verb and resource that clearly distinguishes it from siblings like replay_flow and inspect_flow. The 'HOW IT WORKS' section further clarifies the replacement and anomaly-detection mechanism, reinforcing the tool's unique role.

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 provides explicit prerequisites, including approved=true and the need for a flow_id containing the target_pattern. It offers concrete setup guidance for URL versus body fuzzing, explicitly referencing replay_flow for body insertion, and clearly states the human-approval gate—making when and how to use the tool unambiguous.

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