diff_flows

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

The description presents a read-only comparison returning only differences with masked secrets, but the annotations declare destructiveHint=true. That directly contradicts the implied non-destructive behavior, and the description does not reconcile this discrepancy.

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 front-loaded with the core operation and the list of compared fields, followed by concise usage guidance and return behavior. Every sentence contributes useful information without repetition.

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?

With no output schema, the description adequately explains what is returned: only differences across the listed request attributes, with secrets masked. It could specify the exact diff response structure or no-difference behavior, but it is largely complete for a two-parameter comparison 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 coverage is 100%, and the schema already documents that a and b are request IDs with working/failing examples. The description reinforces that these are request endpoints but adds no syntax or format details beyond the schema.

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 specific operation—diffing two requests—and enumerates exactly what is compared: method, host, path, query parameters, headers, status, and bodies. This clearly distinguishes diff_flows from sibling tools like get_request or summarize_traffic.

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?

It gives explicit usage contexts: comparing a working request with a failing one, or comparing before and after an app change. It does not name alternatives or state when not to use it, so it falls short of a 5 but provides clear guidance.

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