Get notifications

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

Annotations already convey readOnly, idempotent, openWorld, and non-destructive behavior. The description adds the HTTP endpoint and the required read-only scope 'calendars/events.readonly', which is useful context. It does not describe pagination, filtering behavior, or the shape of returned notifications, but the annotation coverage lowers the burden.

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 short and front-loads the essential endpoint and scope information. The repetition of 'Get notifications' from the title is minor and does not significantly hurt clarity.

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 tool with five parameters, no output schema, and a close sibling, this description is incomplete. An agent would still not know when to select this over calendars_find_event_notification, how to form a meaningful query, or what the response contains. Annotations cover safety but not usage context.

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 only 40%, with skip and limit documented but deleted, isActive, and calendarId left to the schema. The description adds that this is a query against /calendars/{calendarId}/notifications, implying calendarId is a path parameter and the rest are query parameters, but it does not explain what deleted or isActive mean or how pagination works.

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 a clear verb and resource: 'Get calendar notifications based on query' with a specific endpoint. It identifies the operation as a read on calendar notifications, though it does not explicitly differentiate itself from the similarly named sibling calendars_find_event_notification.

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 guidance is provided about when to use this tool versus alternatives such as calendars_find_event_notification or calendars_get_calendar_events. The phrase 'based on query' implies filtering but gives no concrete selection criteria or exclusions.

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