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

With no annotations, the description carries the full burden, and it does disclose real behavior: an authenticated session is required, the invitation must target the account's email, and success mutates workspace membership with a role. It does not cover failure modes (expired/reused/foreign-email token), idempotency, or one-time-use semantics for the token, which matter for a membership-mutating call.

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?

A single dense sentence that front-loads the auth precondition before the action and its effect. No filler or redundancy, though it is short enough that structure is a minor consideration.

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?

The description covers the auth precondition and the outcome, and no output schema exists so return values need not be explained. But for a mutation tool with zero annotations and a required parameter at 0% schema coverage, the gaps around token source and failure behavior leave the definition merely adequate.

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 0% and the single required parameter 'token' has no description anywhere. The description only hints at its origin ('invitation issued to this account's email'); it never states that the token is the invitation token from the email, nor anything about length/format expectations (minLength 32, maxLength 100). The schema is doing no work and the description barely compensates.

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?

Specific verb (accept) plus resource (member invitation) and a concrete effect: joining the workspace with the assigned role. It is clearly distinguishable from its invite-side siblings members_invite, members_revoke, and members_remove, which operate on other people's invitations rather than the invitee's own.

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?

The precondition 'Signed-in account session only' tells the agent the required auth state, and the 'issued to this account's email' qualifier implies which invitations qualify. However, no alternative is named (e.g. what to use when an admin wants to accept on someone's behalf, or what to do with a revoked invitation), so when-to-use is implied rather than explicit.

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