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

Adds substantial context beyond the annotations: the bearer-token model means no invite code is ever held, authorization is by id match, and the side effect is asymmetric (grants the human a membership, leaves the calling key's org/project scope untouched). These are non-obvious consequences that the readOnly=false/destructive=false flags cannot convey.

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?

Five tight sentences, front-loaded with purpose, then constraints, then effect. The internal ticket reference (RTSC-686) is noise that earns nothing for an agent, but otherwise there is little waste.

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?

Covers effect, authorization, consent and discovery path, which is what an agent needs to act safely. With no output schema, it stops short of saying what a successful call returns or what an invalid/expired invite looks like.

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% and the description essentially restates the schema ('slug or name, from whoami's pendingInvites'). 'As they'd say it' hints at fuzzy matching tolerance, but there is no detail on accepted forms or failure behavior for an unmatched org name.

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 resource ('Join YOUR HUMAN to an org that invited them') and makes the acting principal explicit, which cleanly separates it from invite_member, list_invites and revoke_invite in the sibling set. An agent can tell what this does and for whom 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 an explicit when ('only invites ADDRESSED to your principal'), an explicit when-not ('never call this unprompted', pasted links go in a browser instead), and routes to whoami for discovering what's waiting. The human-consent precondition is stated as a hard rule rather than implied.

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