Dump the recorded WAMP timeline

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

With no annotations, the description carries the full burden and does well: it discloses that stats are cumulative and survive buffer eviction, that a non-zero 'dropped' means post-cursor eviction, and that lifecycle entries survive a uri filter. It stops short of stating permissions, read-only nature, or whether cursor state mutates, leaving some behavioral gaps.

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?

Four tight sentences, front-loaded with the core return value and followed by the non-obvious semantics (eviction, filter interaction, time units). Every sentence adds information; nothing is redundant filler.

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 correctly explains the return shape (timeline plus per-URI stats) and the meaning of key fields like stats and dropped. Combined with a fully documented 6-parameter schema, it is nearly complete; only the pagination/limit interaction and read-only confirmation are left implicit.

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% so baseline is 3, but the description adds genuine semantics beyond the schema: the interaction between 'uri' and 'kinds' (lifecycle entries survive a uri filter, only kinds exclude them), the meaning of a non-zero 'dropped' relative to the cursor, and clock comparability of timestamps. This meaningfully enriches the parameters.

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?

States a specific verb and resource: 'Return the recorded timeline plus per-URI stats.' The resource ('recorded WAMP timeline') is unique against siblings lol_wamp_record_start/stop, making it clear this is the retrieval counterpart to recording. No ambiguity about what it produces.

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 implied by the pairing with lol_wamp_record_start/stop, and the cursor/dropped semantics hint at polling behavior, but there is no explicit 'use this when...' or exclusion against alternatives like lol_events_poll. An agent can infer the context but is given no routing guidance.

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