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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. 'This action cannot be undone' reinforces irreversibility in plain language, but the description says nothing about notification side effects, permissions, or recurring-event scope, so it adds only modest value beyond 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?

Three short sentences, front-loaded with the operation, and no wasted preamble. 'Use with caution' is largely redundant with the preceding irreversibility warning and the destructiveHint annotation, costing a point.

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?

Adequate for a simple destructive call whose annotations carry the safety profile and whose schema is fully documented. However, it omits meaningful gaps for a calendar deletion tool — behavior on recurring events, whether attendee notifications are suppressed, and confirmation of success (no output schema exists).

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 100%, so all four parameters (event_id, calendar_id, in_workspace, send_notifications) are already fully documented in the schema. The description adds no parameter-level meaning, which is acceptable at this coverage level but earns only the baseline.

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 specific verb and resource ('Delete an event from Google Calendar'), which cleanly separates it from the sibling calendar_create_event, calendar_update_event, calendar_list_events and calendar_check_availability. An agent can identify the operation without opening the schema.

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?

'Use with caution' is a warning, not usage guidance — it does not say when to delete vs. update, what prerequisites exist, or what to do for recurring events. No alternatives or exclusions are named, so the agent gets no routing help beyond the obvious verb.

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