List recent events

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

Annotations already declare a safe, read-only, idempotent operation. The description adds useful behavioral context: default 7-day window, newest-first ordering, limit range, and the meaning of since (only newer events) and types (filter by name). It does not cover pagination beyond the limit or return format, but the added context exceeds what annotations provide.

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 a single, front-loaded sentence with no redundant or filler text. It efficiently packs default scope, ordering, event types, parameter semantics, and usage guidance into a compact form.

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 full schema descriptions and annotations covering safety, the description provides all necessary context: what it returns, default window, ordering, event types, parameter effects, and when to use it. No output schema is needed for a straightforward list.

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%, so the baseline is 3. The description adds semantic meaning beyond the schema: since returns only events newer than the given timestamp, and types filters by event name. Limit range is also reiterated. This is modest but meaningful additional guidance.

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 ('Returns') and resource ('member's event feed'), defines the default scope (last 7 days, newest first), and enumerates the event types. It clearly distinguishes this tool from all siblings, none of which list event feeds.

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 explicitly says when to use it: 'Applies when the user asks what happened recently or whether a post went out.' It also explains how the since and types parameters affect results. No when-not-to-use guidance or alternative tools are mentioned, but no direct sibling exists for this purpose.

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