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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds real extra context: the token is single-use, consuming it marks the invitation accepted, and a role assignment is created as a side effect. That single-use consumption detail is exactly the kind of behavior 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?

Two tight sentences: purpose and effect first, then the usage condition and the consumption semantics. No filler, and the most decision-relevant information is front-loaded.

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?

An output schema exists so return values need not be described, and the annotations cover the safety profile. What remains thin is failure behavior (invalid/expired/already-consumed token) and the nature of the authorization parameter, but for a two-parameter, single-effect call this is nearly complete.

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 description coverage is 0%, so the schema supplies no meaning for either of the two parameters. The description partially compensates by explaining that the token is single-use and gets consumed, but it never explains the 'authorization' parameter (presumably a bearer credential) or where the token originates.

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?

The description states a specific verb and resource ('Accept a pending invitation') plus the consequence ('grant the invitee's first role assignment'), so an agent knows exactly what the call does. It doesn't explicitly name siblings like create_invitation or revoke_invitation, but readOnlyHint=false distinguishing a mutation is clear enough from the wording.

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?

'Call this when an invitee has a valid invite link and wants to join the tenant' gives a clear triggering condition. It lacks explicit exclusions (e.g., what to do if the invite is expired, or that revoke_invitation is the opposite operation), so it stops short of the 5 mark.

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