listEvents

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

The description implies a read-only operation with 'Retrieves', but it does not disclose whether the tool mutates data, requires authentication, or has rate limits. Parameters suggest cursor-based pagination but this is not explained.

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 short sentence with no fluff. However, it is too minimal to be informative, failing to earn its place beyond stating the obvious.

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 lack of output schema, annotations, and parameter documentation, the description is severely incomplete. An agent cannot properly use this tool without additional context on behavior and parameter semantics.

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 input schema has 3 parameters with no descriptions (0% coverage). The description adds no meaning to any parameter, leaving the agent without context on how to use limit, ending_before, or starting_after.

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 clearly states it retrieves a list of event objects, providing a specific verb and resource. However, it does not differentiate from sibling list tools like listCheckouts or listPosts, which also retrieve lists of different resources.

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?

There is no guidance on when to use this tool versus alternatives such as showEvent or other list tools. No context about prerequisites, pagination, or filtering is provided.

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