Get recent stream events

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

Annotations already provide readOnlyHint and openWorldHint. The description adds context about events being 'since this server started' and the note about checking connection status if buffered is empty. No contradiction with annotations.

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 concise (two sentences), well-structured, and front-loaded with the main purpose. No redundant information.

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 the tool has three optional parameters, no output schema, and no nested objects, the description provides sufficient context about event types and buffering behavior. Could be more complete by hinting at the event object structure, but still functional.

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% for all three parameters. The description restates the filtering options but does not add meaningful semantic details beyond what the schema already provides (e.g., type substring, origin platform, limit). Baseline 3 is appropriate.

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 'Return live events (chat, chat commands, follows, subs, bits, raids, donations, heart-rate, etc.) that Lumia has pushed since this server started.' It names the resource and action specifically, and distinguishes from siblings like 'wait_for_event' which is about waiting rather than retrieving.

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 gives optional filtering criteria (type substring, origin) and mentions checking 'status.connected' if nothing is buffered. However, it does not explicitly state when to use this tool versus alternatives like 'wait_for_event' or 'get_state', nor does it provide exclusions.

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