ghl_calendar_notification_delete

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

Annotations already provide readOnlyHint=false, destructiveHint=true, idempotentHint=true. The description adds OAuth scopes (calendars/events.write) which affirm write access but does not disclose behavioral nuances like irreversibility or impact on related entities. It adds some value beyond annotations but not substantial.

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 includes technical details (endpoint, OAuth scopes) that are not essential for an AI agent. The repetition of 'Delete Notification' wastes space. More focused structuring would improve it.

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?

No output schema exists, and the description does not explain what happens upon successful deletion (e.g., confirmation, removed notification). For a destructive operation, this lack of completeness leaves the agent uncertain about the outcome.

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?

Both parameters (calendarId, notificationId) are required but have no descriptions in the schema (0% coverage). The description fails to add any meaning or context for these parameters, leaving the agent without guidance on what values to provide.

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 explicitly states 'Delete Notification', which clearly indicates the action and resource. Among sibling tools like ghl_calendar_notification_create, get, list, update, this delete tool is distinctly identified. No ambiguity, but it lacks additional context like what type of 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 on when to use this tool versus alternatives, prerequisites, or when not to delete. The description only states the action, leaving the agent with no context for appropriate usage.

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