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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the mutation profile is covered. The description adds genuinely new context beyond the annotations: the required permission level, the auth mechanisms (Bearer header vs. key argument), and a credential-handling warning. It does not say what happens to the invitee or whether revocation is reversible.

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?

Purpose is front-loaded in the first sentence, then preconditions, then auth. Three sentences with little waste, though the key-retention warning is largely duplicated verbatim in the schema and could be trimmed.

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, idempotent, open-world tool with no output schema and partial parameter documentation, the description covers purpose, permission requirements, required inputs, and credential handling. What remains unstated is post-revocation behavior (notifications, state of the invite record) and error conditions.

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 coverage is only 50% (key and request_id have descriptions; invite_id and community_id do not), so the description has to compensate. "Requires ... the invitation's community and ID" maps meaningfully onto community_id and invite_id, covering the schema's gap, and the key-auth sentence reinforces the key parameter. It does not explain the types or how IDs are obtained.

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 ("Revoke an outstanding invitation"), which is clearly the inverse of the sibling community_invite_create. However, it never names the sibling or any alternative operation, so the differentiation is implicit in the verb rather than made explicit.

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?

Gives real preconditions for use: owner or moderator access, account scope, and the need for the invitation's community and ID. It stops short of stating when NOT to use it or pointing to the create/list alternatives, but the usage context is clear.

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