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

With no annotations present, the description carries the behavioral burden. It conveys a read-only operation ('Read'), the ordering ('newest first'), and cursor semantics that fetch only newer events. It also signals cost-effectiveness ('the cheap way'), which is useful behavioral context beyond the schema. It does not detail response shape or rate limits, but it is still strong for a simple read tool.

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 tight sentences with no wasted words. The primary purpose is front-loaded, and the cursor usage is explained immediately after, making the description easy to scan and act on.

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 single-optional-parameter read tool without an output schema, the description covers the key operational facts: what events are returned, ordering, and how to paginate with the cursor. It is not fully exhaustive about the response object shape, but the provided information is sufficient for an agent to select and invoke the tool correctly.

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 schema already covers the 'since' parameter well with 'Event-id cursor from a previous call', so the baseline is 3. The description adds extra value by explaining that passing the cursor yields only newer events and frames polling as cheap, giving the agent a clearer mental model of how to use the parameter.

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 a specific verb ('Read'), a clear resource ('the live feed'), and distinctive content types ('bids, dethronements and taunts'). Saying 'newest first' also defines the ordering behavior, making the tool's role unambiguous among the arena sibling tools.

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?

It gives clear context for the intended use: pass the cursor from a previous call to get only newer events, explicitly described as the cheap way to watch for your own dethronement. It does not name alternative tools or state when not to use it, so it misses the bar for a 5.

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