get_new_events

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

Discloses file-based storage, global cursor, and exactly-once delivery across processes. However, does not explicitly state whether events are deleted after draining, leaving ambiguity about data mutation.

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?

Front-loaded with the core purpose; version history adds context but could be more concise. Still efficient overall, with no redundant sentences.

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?

Missing details on return format, pagination, and the behavior of 'peek' parameter. With 7 parameters and no output schema, the description does not adequately cover the tool's input/output semantics.

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?

Only the 'profile' parameter is partially described (default and wildcard). Other 6 parameters (event_type, event_types, chat_id, since_seconds, max_events, peek) have no explanation despite low schema coverage (14%).

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?

Clearly states it drains real-time events from a machine-level event log. Differentiates from sibling tools (mostly CRUD/messaging) by focusing on event consumption with exactly-once delivery.

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?

Provides context on version history, default behavior (current active profile), and option for all profiles. Implicitly indicates when to use (consume events exactly once), but lacks explicit when-not-to-use exclusions.

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