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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the destructive nature is covered structurally. The word 'pending' adds real context beyond annotations (only unaccepted invites can be revoked), but reversibility, required permissions, and whether the invitee is notified are unstated.

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?

One front-loaded sentence, zero filler and no repetition of the title. It is efficient rather than padded; the brevity is under-specification rather than verbosity.

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, irreversible-sounding mutation with no output schema and an undocumented required inviteId, the description should say what happens after revocation and how to obtain the ID. As written, an agent can only guess at preconditions and outcomes.

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?

With only 50% schema description coverage, only orgId is documented ('Organization ID from org_list.'). inviteId has no description anywhere, and the tool description does not explain it or note that it comes from org_invite_list — a gap the description should compensate for but does not.

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 invitation) and narrows scope with 'pending'. It does not distinguish itself from near-siblings such as org_member_remove or regtoken_revoke, which also revoke access objects, so an agent gets a clear action but no sibling routing.

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 guidance on when to use this versus org_member_remove (already-joined member) or invite_accept, and no hint that inviteId must first be obtained via org_invite_list. Nothing tells the agent what condition selects this tool.

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