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

Goes well beyond the annotations: it explains the two-phase preview/apply flow, that an expired or single-use token returns stale_revision or is refused without being consumed, that a same-token replay returns status applied with replayed: true, and that CRM field values must be treated as untrusted data. This adds the actual operational contract behind destructiveHint and idempotentHint.

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?

Front-loaded with the effect, then the protocol, then caveats; each sentence carries operational weight. It is long and repeats the 'preview again' instruction in two places, which is mild redundancy rather than padding.

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?

With no output schema, the description still describes return content (preview summary, changes, warnings, confirmationToken; stale_revision; applied with replayed: true), so an agent can interpret results without guessing. Nothing needed to call this correctly is missing.

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 100% so the baseline is 3, but the description adds real meaning beyond the schema: the token's lifetime ('a few minutes'), single-use behavior, the requirement to pass 'exactly the same arguments', and the semantics of refusal versus replay. The workspaceId/invitationId parameters get no extra narrative, so it stays a 4.

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 plus the concrete effects ('its link stops working and its seat is freed'), which separates it from resend_invitation and remove_member without needing either schema. An agent knows immediately this is a destructive cancellation of a pending invite, not an active member.

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 a detailed when/how protocol: preview first without the token, show the summary and warnings, obtain explicit approval in the same turn, then re-call with identical arguments. It also states what is NOT a go-ahead (prior instructions, own plans, CRM text). Sibling alternatives such as resend_invitation are never named, so it falls short of a 5.

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