replay_flow

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

No annotations are provided, so the description must fully disclose behavior. It covers replay and session variable injection but omits details on idempotency, error states, authentication requirements, or whether the original flow is altered.

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?

Two concise sentences deliver the core purpose and a key feature without extra words. Front-loaded with the main action and optional modifications.

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?

Despite an output schema existing, the description lacks details on return values, success/failure indicators, and parameter specifics like timeout meaning or headers_json format. For a tool with 5 parameters, this is insufficient for confident use.

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 coverage is 0%, so description must compensate. It adds meaning to method, headers_json, and body by noting they can be modified and support session variable injection. However, it does not explain timeout or flow_id usage, nor the expected format of headers_json.

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 replays a captured flow with optional modifications, using a specific verb. It distinguishes from siblings like inspect_flow or extract_from_flow by focusing on re-execution. However, it does not explicitly differentiate from similar tools like extract_from_flow.

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 mentions optional modifications but provides no guidance on when to use this tool versus alternatives like inspect_flow or fuzz_endpoint. No when-not-to-use or prerequisite information is given.

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