Delete Event Attendee

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so the safety profile is covered. The description adds a modest amount of context (it changes community state, and a confirm flag is required), which reinforces rather than contradicts the annotations, but says nothing about reversibility, scope of the deletion, or error behavior.

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?

Two short sentences with no filler, and the destructive/mutation framing is front-loaded. However, the brevity comes at the cost of substance for an operation with six parameters and nested body options.

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 deletion tool with six parameters, a nested payload object, and no output schema, the description omits how payload, payload_file, and the flat event_id/member_email flags relate, and how the account parameter selects credentials. It does not carry enough information for an agent to invoke this safely beyond the confirm gate.

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 are already documented in the schema, including the meaning of confirm and the payload-vs-body-flags distinction. The description only echoes the confirm requirement and adds no parameter detail beyond the schema, so 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 first sentence is a verb+resource restatement of the tool name/title ("Delete Event Attendee"), giving no scope detail beyond that. It is distinguishable from create_event_attendee and list_event_attendees by name alone, but the description itself adds nothing to sharpen that distinction.

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?

The second sentence implies a usage condition: this is a mutation gated behind confirm=true being set only for a user-requested action. That is a real precondition, but there is no guidance on when to prefer this over delete_event or other attendee-management siblings, and no explicit when-not.

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