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

No annotations are provided, so the description carries the full behavioral burden. It discloses the authorization requirement ('Platform operators only') and the state boundary ('Existing accounts are unaffected'), which is valuable context for a destructive-sounding mutation. It does not say whether revocation is reversible or immediate, but covers the most important behavioral trait.

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 tightly written sentences with no waste. The role restriction and the effect on existing accounts are both front-loaded as the most decision-relevant facts.

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?

Adequate for a simple one-parameter mutation: role gating and account impact are stated, but the meaning of the 'id' parameter and the reversibility/immediacy of revocation are missing. No output schema exists to cover return behavior, so the description leaves a modest gap.

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 0% and the description says nothing about the 'id' parameter. With one required UUID parameter and zero schema descriptions, the description must compensate to identify what the ID refers to, and it 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?

Specific verb+resource: 'revoke an unused invitation'. It also scopes the effect ('Existing accounts are unaffected') to distinguish it from account-affecting operations. An agent can tell it apart from invitations_create and invitations_list immediately.

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 'unused invitation' phrasing implies a precondition and 'Platform operators only' signals a role requirement, so some usage context is conveyed. However, there is no explicit when-to-use vs alternatives (e.g., members_revoke or credentials_revoke), and no stated exclusions beyond 'existing accounts are unaffected'.

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