Get notification

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

The annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the required OAuth scope 'calendars/events.readonly' and the REST path, which is useful context beyond annotations. It does not disclose return format, error behavior, or any side effects, but those are less critical given the 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 short but awkwardly constructed: 'Get notification Find Event notification by notificationId' reads like a concatenation of the title and a separate purpose phrase. It front-loads the main intent but wastes a few words on redundancy.

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?

This is a simple two-parameter read operation, and the description provides the endpoint and scope, which is reasonably complete for a low-complexity tool. However, it lacks context about what an event notification is, how to discover one, or what the response contains, and the absence of an output schema makes those gaps more noticeable.

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 0%, so the description must compensate. It mentionse notificationId in text and exposes both calendarId and notificationId as path placeholders in the endpoint, giving some clue. However, it does not explain what calendarId represents or what formats/constraints the values must satisfy, leaving an agent partially guessing.

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 specific verb ('Find'), a resource ('Event notification'), and an identifier ('notificationId'), so the action is clear. The endpoint template reinforces the exact resource being accessed. It does not explicitly differentiate from the similarly named sibling 'calendars_get_event_notification', but the behavior itself is 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?

There is no guidance on when to use this tool versus alternatives, and no mention of exclusions or prerequisites. The description merely states what the tool does, leaving the agent to infer usage context from the endpoint and name.

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