List Events

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the agent knows this is a safe, read-only operation. The description adds value by specifying the returned fields (title, start/end times, ref handle) and the relationship to update/delete tools. It does not contradict annotations and provides context beyond the structured hints.

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 sentences, front-loaded with the core action, and contains no redundant or irrelevant content. It efficiently conveys the tool's purpose and key behavioral details.

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 list tool with two optional parameters, an output schema, and comprehensive annotations, the description sufficiently covers purpose, returned data, and linkage to sibling tools. It does not need to elaborate on return values or error handling given the output schema exists.

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% for both 'count' and 'daysAhead', including defaults and maximums. The description's mention of the look-ahead window (30 days default, up to 365) aligns with the schema and adds no new information. Since the schema fully documents parameters, the baseline of 3 is appropriate.

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 the tool lists upcoming calendar events within a configurable look-ahead window. The verb 'lists' and resource 'calendar events' are specific, and it naturally distinguishes itself from sibling tools like list-calendars (which lists calendars) and event mutation tools (create/update/delete).

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 provides clear usage context by explaining the look-ahead window and that returned ref handles are used by update-event and delete-event. It implicitly guides when to use this tool (to get event handles for mutation), though it does not explicitly state when not to use it or mention alternatives like list-calendars.

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