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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description goes beyond them by disclosing that guests are emailed a cancellation and that the action cannot be undone, plus a human-confirmation requirement. That is meaningful consequence disclosure an agent cannot get from the annotations alone.

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?

Three short sentences, front-loading what is deleted, then the side effects, then the safety requirement. Every sentence earns its place with no filler.

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 destructive, open-world mutation with no output schema the description covers consequences and confirmation well, but it leaves the parameter story thin (calendarId unaddressed) and gives no guidance on recurrence/occurrence identification or error cases when no guests exist.

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 33%: mailbox is documented in the schema (with a pointer to list_authorized_mailboxes), but eventId and calendarId carry no description anywhere. The description adds no parameter meaning — it doesn't explain how to identify an occurrence or which calendar defaults apply — so it fails to compensate for the coverage gap.

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?

States a precise verb+resource and even narrows the scope to 'one event or one occurrence', which tells an agent it is deleting a single calendar entry rather than a whole calendar (delete_google_calendar) or a task. It does not name an alternative sibling explicitly, so it stops short of a 5.

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?

Gives one clear operational rule — ask the user to confirm before calling — which is real usage guidance, but says nothing about when to prefer this over delete_outlook_calendar_event or when calendarId vs the default calendar matters. Usage context is implied rather than spelled out.

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