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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real substance: the email-match requirement is a hidden failure mode not captured anywhere in structured fields, and it specifies that re-accepting returns the org rather than erroring. It stops short of describing the failure response when the email doesn't match.

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?

Three short sentences, no filler, with the action and its precondition front-loaded. Every clause carries information the agent needs.

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 two-parameter mutation with no output schema, the description covers the action, the auth precondition, idempotent behavior, and roughly what comes back ('returns the org'). Only the error behavior on an email mismatch is left unstated.

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% — `org` is documented in the schema, `token` is not. The phrase 'invite link' implicitly tells the agent where the token comes from, which is a genuine addition, but the description never addresses the token or the org default directly.

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 outcome — 'Join the org an invite link is for' — which is clearly distinct from sibling read operations like cloud_invites_get or cloud_org_list. 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 concrete precondition ('The invite must be for the email you signed in with') that governs when the call will succeed, and clarifies the already-accepted case. No sibling alternative is named, but there isn't a plausible competing tool for this action.

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