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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the link itself is the credential (whoever holds it acts under that name), all acts are attributed to that name, and out-of-role attempts are refused and logged. It stops short of stating token expiry, revocation semantics, or required caller permissions.

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?

The opening line front-loads the two invite paths, and the role list is compact and information-dense. The closing sentence about one-sentence denial refusals being 'reviewable, like everything else' is workspace policy padding rather than tool-specific information, slightly diluting the payload.

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, the description must carry the return contract, and 'Effects: member token minted' only half does so — it never says the minted link/token comes back in the response, which is precisely what the caller needs in order to share it. Missing too is any statement of who may call this or whether an existing member with that name is updated or rejected.

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, and the description does add real value by defining what each role can do (controller vs clerk vs viewer) rather than leaving bare enum names. Against that, it introduces an 'owner' role that the schema enum does not accept, which could lead an agent to pass an invalid value, and it adds nothing about the email/name interaction beyond the schema.

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 (invite a member to this workspace) and immediately clarifies the two mechanisms: email invite via Google sign-in, or a member token link. An agent can distinguish it from core_members (listing) and core_revoke_member (removal) by name alone, though the description never names those siblings explicitly.

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?

It gives real guidance on choosing the email path versus the token path, and the role list helps pick a role value. However, it never says when to use this tool versus core_members or core_revoke_member, nor does it state preconditions such as who is permitted to invite or what happens if the name already exists.

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