list_events

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

The description discloses that the operation returns paginated results and that filters are optional. However, since no annotations are provided, the description carries the full burden; it does not explicitly confirm read-only behavior or any permission requirements, though 'list' implies it.

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 two short sentences, front-loaded with the action and resource. Each sentence adds necessary information: what it lists and how results are returned (paginated). No redundant wording.

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 no output schema, the description does not specify the structure of returned events, but it covers the core purpose, filters, and pagination. For a simple list tool with optional filters, this is reasonably complete, though a note about default ordering or fields could improve it.

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 provides full descriptions for all six parameters, so the baseline is 3. The description adds conceptual grouping by mentioning 'date range' (combining startDate and endDate) and clarifies that filters are optional, which adds slight value 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?

The description uses the specific verb 'List' with the resource 'upcoming events', and explicitly mentions optional filters by organizer, department, or date range. This clearly distinguishes it from sibling tools like 'list_contacts' and 'get_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?

The description implies the tool is used to list events, with optional filters. It provides clear context but does not explicitly mention when to prefer this over alternatives like 'get_event' for a single event or when not to use it. No exclusions or alternative tool references are given.

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