Delete Invitee Data

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

Annotations already declare destructive=true, idempotent=false and openWorld=true, but the description adds genuine context beyond them: it states the action changes Calendly state, requires an explicit confirm=true gate, and needs the data_compliance:write scope. The auth/confirmation requirements are exactly the kind of behavioral detail annotations cannot express.

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 brief sentences, front-loaded with purpose and followed by the confirmation gate and scope requirement. There is essentially no filler, though the opening restatement of the title is near-redundant.

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, no-output-schema tool, the definition covers the mutation effect, the confirmation requirement and the required scope, while annotations carry the irreversibility signal. It omits detail on what exactly gets deleted (email-scoped invitee records) and permanence, but nothing critical is missing for correct invocation.

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 80%, so the schema already documents the parameters (account, confirm, payload, payload_file). The description only echoes the confirm=true requirement that the schema itself states, adding no syntax or format detail beyond it. Baseline 3 is appropriate.

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's first sentence is the title restated verbatim ('Delete Invitee Data'), so it conveys the verb+resource but adds no elaboration. It does make clear this is a delete operation on invitee data, but does nothing to distinguish it from close siblings like delete_scheduled_event_data or delete_contact.

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 context is given for when to use this tool versus the other delete tools (delete_contact, delete_recap, delete_scheduled_event_data). The confirm and scope mentions are prerequisites, not usage guidance, so an agent gets no routing help.

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