Drain held events (free)

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

With no annotations, the description must disclose side effects, but it does not clarify whether draining is destructive or whether events are removed from the mailbox. The word 'drain' implies consumption, but the description says 'Collect' without stating if repeated calls return the same events or if events are deleted.

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 only two sentences and gets straight to the point, front-loading the main action. It avoids redundancy but includes a useful tip, making it 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?

The tool has three parameters and no output schema, so the description should cover the return format and all parameter roles. It only partially addresses `since` and gives no indication of the response structure, making it incomplete for safe usage.

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 description explains the `since` parameter as a 'last seen event id' for incremental drains, which is helpful. However, the required `watchId` and `secret` parameters are not described, leaving users to infer their roles from the tool's context.

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 'Collect everything the watch caught' which clearly identifies the tool as a fetch/drain operation for watch events. The title 'Drain held events' reinforces the purpose, and the mention of 'watch' distinguishes it from coordinate-related siblings.

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 provides context that this works with 'zero infrastructure' and the 'mailbox pattern,' suggesting it is the lightweight option. It also gives a concrete usage tip for incremental drains via `since`, but does not explicitly contrast with alternatives like coord_events or state when not to use this tool.

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