fetchCalendarEvents

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

Annotations already declare readOnlyHint=true, so the description's 'Fetch' aligns. The description adds the connector requirement and the time scope, but does not elaborate on error behavior if the connector is missing or on pagination limits. It meets the baseline but lacks extra context beyond annotations.

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 only two sentences, each conveying essential information (fetching events, time range, prerequisite). No extraneous words, and the most important action is front-loaded. It is an model of conciseness.

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?

With no output schema, the description briefly mentions return type ('Returns events' ) but omits details like structure (e.g., summary, start, end). However, the tool's purpose is simple, the parameters are well-defined, and an AI agent can infer the likely output format. Minor gap, but overall sufficient.

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 provides full descriptions for all three parameters (daysAhead, maxResults, calendarId). The description only reiterates 'next N days' which matches daysAhead, adding no new meaning. Schema coverage is 100%, so 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 verb 'Fetch' and the resource 'upcoming Google Calendar events'. It specifies the scope (next N days) and a prerequisite (Google Calendar connector connected). There are no sibling tools with similar purpose, so it is well-distinguished.

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 explicitly mentions a prerequisite (connector required) and implies the tool is for upcoming events. However, it does not provide guidance on when not to use this tool (e.g., for past events or other calendars) or mention alternatives, which is a minor gap.

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