List calendar events

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

Annotations already declare read-only, idempotent, non-destructive behavior. Description adds ordering by start time and return structure. However, it does not clarify timezone handling, pagination beyond limit, or if 'upcoming' includes events starting now.

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?

Description is short with two clear sentences plus parameter/return details. Every sentence adds value. Could be slightly more structured with bullet points, 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?

The description provides a return format outline but omits details like meaning of 'count' (total vs filtered) and full structure of nested objects (e.g., attendees). For a simple tool, it is adequate but not exhaustive.

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%, and the description copies parameter details from schema without adding new meaning (e.g., defaults, ranges). Baseline 3 applies.

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 'List the user's upcoming calendar events (ordered by start time)', specifying the exact verb, resource, and ordering. It differentiates from sibling tools like teams_get_event (single event) and teams_create_meeting (create).

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 usage for listing upcoming events but does not explicitly compare to alternatives (e.g., when to use teams_get_event). No guidance on when not to use this tool or prerequisites.

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