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

With no annotations, the description carries the full burden and does meaningful work: 'permanently' signals irreversibility, 'Platform operators only' signals the permission requirement, and it explicitly scopes out side effects on the account and invitations. It still omits confirmation behavior and what the response looks like, so it is not complete.

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 tight sentences with zero filler; the destructive action and its audience restriction are front-loaded, followed immediately by the scope caveat.

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 single-parameter destructive mutation with no annotations and no output schema, the description covers irreversibility, permission scope, and what is left intact — enough to call it safely. The remaining gap is that the identifier parameter is never disambiguated.

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?

There is one required parameter ('id') with 0% schema description coverage, and the description does not say what that id identifies — a waitlist entry, an applicant, or an account. The phrase 'an applicant's waitlist information' only weakly hints at the referent, leaving real ambiguity about what value to pass.

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 gives a specific verb ('permanently remove') and resource ('an applicant's waitlist information'), and explicitly delimits scope by stating it does not delete the account or invitations. That negative framing cleanly separates it from siblings like account_delete and invitations_revoke.

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 names a clear audience constraint ('Platform operators only') and rules out adjacent actions, which implicitly routes account/invitation removal to those other tools. However, it never names an alternative tool or states positively when this is the correct call versus waitlist_update or support_deny.

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