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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is partly covered. The description adds genuinely new context beyond that: a mandatory confirmation-token workflow, an explicit user-consent gate, and permission/role prerequisites. It does not explain retry semantics despite idempotentHint=false, which is the remaining gap.

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?

Four sentences, all load-bearing and front-loaded with the outcome before the sequencing and permission details. Dense but not padded; the confirmation-flow sentence is necessarily long but earns its place.

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?

An output schema exists, so return values need not be described, and the description covers the confirmation prerequisite, consent gate, and permission requirements for this mutation. The only loose end is organizationId scoping in multi-org contexts.

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% (just requestId), so the description must compensate and largely does: it disambiguates memberId ('the member id from list_members, not the user id') and explains where confirmationToken comes from via the preview_operation flow. organizationId's scope is still not clarified, so it falls just short of full compensation.

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+resource+effect: returning access to a suspended member of the organization. It is immediately distinguishable from sibling suspend_member and change_member_role without opening any 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 prescribes the prerequisite flow: call preview_operation with tool 'reactivate_member' and these arguments, show the plan to the user, then call this tool only after explicit agreement. It also names the required permission (organization:manage) and the owner role, leaving nothing to inference.

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