Correlate LCU WAMP and CDP console timelines

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

No annotations exist, so the description carries the full burden. It discloses that it merges two event sources chronologically and what question it answers, which is useful behavioral context, but it omits key traits such as the prerequisite recordings, whether the operation is read-only, and how the three output formats differ.

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?

A single tightly written sentence that front-loads the core action and the diagnostic payoff with no wasted words. Slightly dense but efficient.

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?

There is no output schema and no annotations, so the description must do more of the work. It does not explain where the source data comes from (requiring prior recording sessions), nor does it describe the narrative/events/summary output shapes, leaving meaningful gaps for a six-parameter correlation 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 description coverage is 100%, so all six parameters (limit, since, until, format, levels, uriPrefix) are already documented in the schema, including the enum for format and levels. The description adds no syntax or semantic detail beyond what the schema provides, so the baseline 3 applies.

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+resource combination ("Combines WAMP recorder events and CDP console entries into a chronological timeline") and further states the diagnostic questions it answers. This is clear and distinguishable from recording/tailing siblings, though it never names the dump/tail tools it consumes.

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?

Usage is only implied through the diagnostic framing ("whether the client emitted an event and where the frontend broke"). There is no explicit statement of when to reach for this over lol_wamp_record_dump or lol_cdp_console_tail, and no mention of the prerequisite that recorders must already be running.

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