poll_events

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

No annotations are provided, so the description carries the full behavioral burden. It says events are polled from a buffer but does not disclose whether polling consumes events, blocks, returns immediately, respects ordering, or interacts with subscriptions. The presence of an output schema reduces the need to describe return values, but core polling semantics remain unexplained.

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?

A single front-loaded sentence with no wasted words. It states the action and source immediately.

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?

For a tool with two undocumented parameters, no annotations, and sibling event-management tools, the definition is too sparse. The output schema covers return values, but the description should explain polling behavior, parameter effects, and relationship to subscribe/unsubscribe tools.

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 description coverage is 0%, and the description adds no meaning for max_events or event_types. The parameter names are somewhat intuitive, but the definition provides no filtering, limit, or format semantics beyond the raw 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?

States a specific verb and resource: polling events from the EventManager buffer. It is clear what the tool does, though it does not differentiate itself from sibling event tools such as subscribe_events or unsubscribe_events.

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 no guidance on when to use polling versus subscribing, nor any prerequisites or alternatives. The purpose implies usage, but the agent must infer all selection criteria.

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