list_events

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

No annotations provided, and the description does not disclose behavioral traits such as being a read-only operation, authorization requirements, rate limits, or pagination behavior. For a list tool, stating it 'detects events' could imply some processing, but the behavior is not sufficiently transparent.

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 very concise, consisting of a single sentence that directly states the main purpose. Information is front-loaded. However, it could be slightly more structured with explicit mention of key parameters, but overall efficient.

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?

Given the tool has 7 parameters, no annotations, and no output schema, the description is incomplete. It only addresses one filter (tier) and omits details on pagination, search, event types, and search modes. For a comprehensive list tool, this leaves significant gaps in understanding usage.

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% with descriptions for all parameters, so the schema already provides meaning. The description adds no new parameter semantics beyond mentioning 'tier' which corresponds to tier_status, already documented in the schema. Baseline 3 is appropriate as the description does not enhance understanding beyond the 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?

Clearly states the tool lists events and describes them as 'message clusters'. Verb 'List' and resource 'events' are specific, and the description mentions filtering by tier, adding purpose clarity. However, it does not explicitly differentiate from sibling tools like 'get_event' which retrieves a single event.

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 some guidance on filtering by tier (rumor, unconfirmed, confirmed, verified), implying when to use this tool for filtered event listing. However, lacks explicit when-not-to-use or alternative tool mentions, such as using 'get_event' for a specific event or other list tools for different entities.

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