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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds one genuinely useful fact beyond that — the Stripe subscription is not canceled, only the membership — but it does not say whether access is revoked immediately, whether the member is notified, or how to undo it.

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 padding and the action front-loaded. It is efficient, though the terseness comes partly from omitting information an agent needs rather than from disciplined editing.

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?

This is a destructive, zero-required-parameter tool with no output schema and only a third of its parameters documented. The description should at minimum clarify which identifiers are required and that a site id is implied; as written it leaves the critical call-shape question unanswered.

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% (only "id" is documented, as site id). The description mentions customerId and email but omits the site id entirely, so an agent cannot tell whether the call needs a site context plus an identifier or an identifier alone — and with zero required parameters the ambiguity is real, not theoretical.

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 a member") and adds an identifier hint, so the core action is unambiguous. It does not distinguish itself from adjacent siblings such as revoke_site_invite, set_member, or invite_site_member, which is the missing piece for 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?

There is no when-to-use / when-not guidance and no named alternative, even though revoke_site_invite and set_member sit in the same sibling set and could plausibly be confused with it. The only hint, "Stripe billing continues," is a behavioral note rather than a usage rule.

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