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

Annotations already cover the safety profile (destructive, idempotent, not read-only). The description adds real context beyond them: the verified-email prerequisite, the token-handling rule ('accepted from the invitation link and never echoed'), and the membership-control model. It doesn't state what success/error looks like, but no output schema exists and the safety dimension is well covered.

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 short sentences, front-loaded with the consent gate and prerequisite before the softer explanatory guidance. Every sentence carries relevant information; only the 'explain that admins control membership' sentence leans toward instructional filler.

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 mutation tool with annotations covering safety and no output schema, the description supplies the prerequisite, the consent requirement, and token handling. The main omission is failure behavior (expired/used token), but the structured fields carry most of the rest.

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 50%: 'confirm' is described in the schema, but 'token' only has a regex pattern. The description partially compensates by explaining where the token comes from and that it is never echoed, but it adds no format or source detail beyond that. Baseline 3 is appropriate.

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 ('Join a team' by accepting an invitation) and immediately distinguishes it from sibling tools like invite_workspace_members, revoke_workspace_invitation, and resend_workspace_invitation. An agent can tell what this does without opening the 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?

Gives a clear gating condition ('only on an explicit user request to accept their invitation') and a prerequisite ('The connected account must have the invited verified email'). It does not explicitly name alternative tools for the invite/revoke side, so it stops short of a full comparison.

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