reverse_analyze_live_api_flow

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

With no annotations provided, the description carries the full burden of disclosing side effects and operational traits. It mentions running a workflow but does not disclose that it may replay traffic (based on parameters like run_replay, replay_use_proxy) or any state changes. The description is too sparse to inform an agent of potential impacts.

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 concise at two sentences, but it is under-specified for a tool with 12 parameters and a complex workflow. It front-loads the action but omits necessary context, making it too short to be considered appropriately sized.

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 tool with 12 parameters, an output schema, and no annotations, the description is grossly incomplete. It does not explain what the workflow entails, what the summary/report contains, or how parameters influence behavior. The presence of an output schema does not compensate for the lack of operational guidance.

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 only 8% (only snapshot_format has a description). The description adds no information about any of the 12 parameters, such as limit, advance, run_replay, or path_keywords. It fails to compensate for the low schema coverage, leaving parameter meanings entirely to the agent's inference.

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 states a verb ('Run') and a resource ('task-oriented live API reverse-analysis workflow'), but 'task-oriented' is vague and does not specify what the task is. It also does not differentiate from sibling tools like reverse_analyze_live_login_flow or reverse_analyze_live_signature_flow, leaving ambiguity about its scope.

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 instruction 'Read summary/report first and expand evidence only as needed' gives a workflow hint but does not explain when to choose this tool over alternatives. No exclusions or alternative references are provided, so an agent cannot decide between this and similar analysis tools.

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