get_recent_events

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

No annotations are provided, so the description carries the full burden. It discloses content shape and newest-first ordering, but says nothing about pagination behavior beyond the schema's limit, permission requirements, or read-only nature — a modest but real gap for an unannotated 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 sentences, zero waste: the first states what the stream is and how it is ordered, the second states when to pick it over the alternative. Nothing is repeated and the key scoping detail is front-loaded.

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 simple read-only list tool with two optional params and no output schema, the description covers the resource, its contents, and its ordering well enough to call correctly. Minor remaining gap is that it doesn't characterize the payload fields of an event, which is not documented anywhere else.

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 100%, so both parameters (type filter and limit with a 200 maximum) are already documented in the schema. The description adds no filter syntax or default-limit context beyond that, so the baseline 3 applies.

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 names the resource precisely ('the raw agent event stream'), enumerates its contents (tool calls, prompts, session starts/stops) and states the ordering (newest first). It also implicitly distinguishes itself from the summary-style sibling, so an agent can tell what it returns without opening the schema.

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 an explicit selection rule: use it when you need to know exactly what has run 'rather than a summary'. That routes the agent away from the summary tool, though it does not name the sibling explicitly or state any exclusion conditions (e.g. volume constraints).

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