Delete Scheduled Event Data

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context the annotations lack: the required OAuth scope (data_compliance:write) and the confirm=true guard for the specific requested action.

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 terse sentences, front-loaded with the destructive action before the preconditions. Slight redundancy in restating the title, but there is no padding or throat-clearing.

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, zero-required-parameter tool with no output schema, the description covers the key call-time essentials: confirmation flag and required scope. It leaves the payload/payload_file/body-flag relationship and the time-window semantics to the schema, which is acceptable at 100% coverage.

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 six parameters (account, confirm, payload, start/end time, payload_file) are already documented in the schema, including the mutual-exclusion between payload and payload_file. The description only echoes confirm=true, adding nothing beyond the schema. Baseline 3 applies.

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+resource, 'Delete Scheduled Event Data', so the operation is unambiguous. It does not, however, distinguish itself from the very similar sibling delete_invitee_data, which an agent choosing among data-compliance deletions would want clarified.

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?

It supplies operational preconditions (confirm=true, scope data_compliance:write) but gives no when-to-use vs. alternatives guidance, e.g. when to reach for this rather than delete_invitee_data or cancel_event. Usage is implied rather than directed.

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