fetchCalendarEvents

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

With no annotations, the description carries the full burden of behavioral disclosure. It does mention that the return format is 'Notification format,' which is useful context. However, it does not explain default time ranges, result limits, ordering, authentication needs, or how the optional 'since' parameter interacts with 'upcoming and recent,' leaving ambiguity about the tool's actual behavior.

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. The first states the core action and scope, and the second specifies the return format. Every sentence is purposeful and contributes directly to understanding the tool, with no redundant or filler content.

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 tool is simple with one optional parameter and full schema coverage, so the schema carries some weight. However, the description introduces ambiguity with 'upcoming and recent' — it does not define what counts as recent, what the default time window is when 'since' is omitted, or how many events will be returned. Without an output schema, the mention of Notification format is helpful but insufficient to fully understand the response structure.

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 description coverage is 100%, with the 'since' parameter clearly documented as 'ISO 8601 timestamp. Only returns events starting after this time.' The tool description adds no additional meaning about the parameter, so it does not go beyond the schema. Baseline 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 states 'Fetch upcoming and recent calendar events' with a specific verb 'fetch' and resource 'calendar events,' clearly distinguishing it from sibling notification tools like fetchSlackNotifications or fetchGithubNotifications. It also specifies the return format, 'a list of meetings in Notification format,' making the tool's function unambiguous.

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?

No explicit when-to-use or alternative guidance is provided. The tool's purpose is implied by its name and sibling context (fetching calendar notifications), but there is no statement of exclusions, prerequisites, or when to choose this tool over other notification fetchers. Usage is only implicitly conveyed.

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