drain_events

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

No annotations are provided, so the description carries the burden. It discloses that events are cached and drained (consuming them on retrieval), which is key behavioral info. However, it doesn't mention whether draining clears the buffer, if events could be lost if not drained in time, or whether invoking this is non-destructive in terms of the underlying browser state. The drain semantics are partially implied but not fully explicit.

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 that are front-loaded with the core purpose (pull cached CDP events) and followed by the return structure. No wasted words. Could arguably merge the return-type detail more smoothly but it's efficient and structured well.

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?

Given 0 params and no output schema, the description does explain the return shape which is the main missing piece. However, for a stateful 'drain' operation, it could be more complete about buffer semantics (does drain clear the cache? what happens with old events?), rate limits, or whether events persist across invocations. The description tells you what comes back but not the lifecycle guarantees.

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?

The tool has 0 parameters, and schema coverage is 100% with an empty properties object. The description correctly compensates by explaining what the return value contains, even though there's nothing to explain about inputs. The event structure {method, params, sessionId, tabId} is documented, which adds meaningful information beyond the empty 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 clearly states the verb (drain/pull) and resource (cached CDP events since last drain). It specifies the return type is a list and describes each event's structure. It doesn't explicitly distinguish from siblings, but the concept of draining buffered events is distinct enough among the sibling tools listed.

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 implies it's used to retrieve buffered CDP events accumulated since the last drain, but doesn't explicitly state when to use it vs. the cdp tool or other event-related tools. The timing ('since last drain') is clear, but there's no explicit guidance on when this is the right choice over alternatives.

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