Reactivate a member

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

Annotations only say non-readOnly, non-destructive, non-idempotent; the description adds the crucial gated two-step confirmation workflow, the permission/role requirements, and the ID disambiguation that can cause silent mis-targeting. This is exactly the extra context annotations cannot carry.

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?

Three front-loaded sentences, each carrying distinct load: purpose, ID semantics, then the confirmation gate plus permissions. No repetition of schema or annotation 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?

Covers the prerequisites, workflow, and ID source with no output schema to explain. Minor gaps: no mention of edge cases (already-active member) or what the confirmation token's validity/lifetime is, but nothing that would cause a wrong call.

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 25%, but the description compensates for the two non-obvious params: memberId's provenance ('from list_members, not the user id') and confirmationToken's acquisition procedure via preview_operation with the matching tool name and arguments. Only organizationId is left implicit, which is unambiguous.

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 ('Give a suspended member their access to the organization back'), which makes it clear this is the inverse of suspend_member. An agent can identify the operation without opening the schema.

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?

Explicitly names the alternative for obtaining the ID ('from list_members, not the user id'), mandates calling preview_operation first, and gives the exact gating condition: only after the user explicitly agrees. Prerequisites (organization:manage, owner role) are stated.

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