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

Annotations already declare the safety profile (non-readOnly, non-destructive, non-idempotent). The description adds useful context that an approval workflow governs the operation and that business workflow approvals always apply, but the phrasing about configurable MCP approval requirements is vague and it omits what state the user must be in, whether prior roles/permissions are restored, and what errors occur on repeat calls despite idempotentHint=false.

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 short sentences with the action front-loaded and no filler. The second sentence is a bit roundabout in wording but still short and relevant.

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 one-parameter mutation with an output schema and annotations, the description covers purpose and the approval caveat, but it omits the precondition state, the effect on the user's access, and failure behavior. Adequate but with clear gaps an agent would want filled.

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 description coverage is 0% and the description never mentions the single required parameter. It does not clarify whether `id` is the organization-user record id or the underlying user id, nor its UUID format, leaving the agent to infer from the name alone.

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?

The description states a specific verb and resource ("reactivate a user"), which is clearly distinct from the mutation siblings like suspend_organization_user or update_organization_user. However, it never explicitly names those siblings or the state precondition that distinguishes reactivation from other user operations.

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?

There is no explicit guidance on when to call this versus suspend_organization_user, invite_organization_user, or update_organization_user. The second sentence discusses approval policy but says nothing about the conditions that make reactivation the right tool or what preconditions (e.g., user currently suspended) must hold.

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