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

Annotations only declare readOnlyHint=false and destructiveHint=true; the description adds substantial context beyond that: the target user is notified by email and in-app, their workspace role is unchanged and viewers stay read-only, and the first call is a no-op preview. It also discloses token behavior (single-use, short-lived), which an agent cannot infer from the annotations.

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-loads the action and prerequisite, then the critical two-step protocol, with no filler sentences. It is dense and slightly repetitive with the schema's confirmationToken description, which is why it stops short of a 5.

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 prerequisites, side effects (notifications), safety caveats, and the confirmation flow, which is strong for a 3-parameter mutation. However, with no output schema, it never says what the preview or success response contains (e.g., what fields the agent should surface to the user), leaving a gap for a two-step approval workflow.

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 the schema cannot convey: confirmationToken must be paired with the SAME arguments, is single-use, and expires after a few minutes. It also cross-references where valid userId values come from (listOrganizationUsers / listBetaManagers).

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: 'Assigns a workspace member as a manager of this beta project.' That is clearly distinguishable from siblings like removeBetaManager, listBetaManagers, and inviteTesters, so an agent can select it without opening other schemas.

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 both prerequisites ('must already be a member of the workspace (see listOrganizationUsers)') and an explicit exclusion ('inviting new members to the workspace is not possible over MCP'), pointing to the right alternative. It also spells out the two-step when-to-call sequence: first without a token to get a preview, then again only after explicit user approval.

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