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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, but the description still adds substantive non-annotation context: what state is restored (org visibility plus prior role), which subject types are rejected, and the permission ceiling for admins. The one gap is failure/error behavior when an admin attempts a suspended owner/admin, which is implied but not spelled out.

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 action and effect, then constraints, then the parameter source — no filler sentences. It is dense to the point of being slightly hard to scan due to heavy capitalization and stacked em-dash clauses, but nothing is redundant enough to cut.

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 and only one parameter, the description covers what an agent needs: what changes, who is allowed, who is rejected, and where the id comes from. Return value shape is unspecified, but the annotations carry idempotency and safety, so the remaining gap is minor.

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% and the single parameter is documented, so the baseline is 3. The description earns one step above baseline by disambiguating the id as a PERSON member id (not an agent id) and widening the provenance hint to list_members/whoami, which the schema alone only partially states.

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 (reactivate) and resource (a suspended PERSON), plus the concrete effect: restores org visibility and prior role. It explicitly carves out the AGENT case as impossible, which no sibling name or schema conveys, so an agent can distinguish this from retire_member, suspend_member, and invite_member at a glance.

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 the positive trigger (a suspended PERSON), the exclusion (an AGENT, since retire is terminal and nothing remains to reactivate), and the authorization rule (through the human principal; an admin may reactivate ordinary members only, never a suspended owner or admin). It also routes to list_members/whoami to obtain the id, so no inference is needed to decide whether this tool applies.

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