calendars_delete_event_notification

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

The description does not contradict the annotations (destructiveHint=true, readOnlyHint=false), and the word 'Delete' is consistent with those flags. However, it adds no extra behavioral context—such as whether deletion is permanent, if it affects the event, or any side effects. Given annotations already convey destructive intent, the description could add value by explaining consequences but doesn't.

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 words, which is under-specification rather than concise. It provides no structure or front-loaded context. Every word is minimal, but the tool needs more explanation to be useful.

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 and a destructive operation, the description should specify what happens on success or failure, whether the notification must exist, and the impact of deletion. None of this is present. The tool is essentially a bare operation with no contractual details.

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%, meaning the parameters (calendarId, notificationId) have no descriptions. The description should compensate but says nothing about what these IDs refer to or how they relate to the notification. An agent cannot infer parameter meaning from this description.

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 'Delete Notification' is extremely vague and does not specify that it operates on calendar event notifications. It fails to distinguish from other delete tools like calendars_delete_calendar or calendars_delete_event. The tool name provides more clarity than the description, but the description itself is little more than a truncated version of the name.

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, what alternatives exist, or any conditions that should trigger its use. The description simply states the action without context. No mention of prerequisites, such as the notification needing to exist, or whether this deletes only event-specific notifications.

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