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

Annotations already declare readOnly=false, idempotent=false and openWorld=true, so safety profile is covered. The description adds genuinely new context: the no-sign-in path for open invites and the fact that a conversation id is returned (relevant since no output schema exists). It does not mention what happens on a closed/expired invite.

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, outcome-first, with the auth caveat and return value each earning their place. No 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?

The description does the important work of stating the return value in the absence of an output schema and flags the auth nuance. It is still thin for a mutating, open-world tool that creates a conversation: invite link format, failure modes, and the meaning of 'agent'/'token' are unaddressed.

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 only 50%, and the undocumented 'link' parameter (the sole required one) gets no explanation of its format or origin in the description. The 'open invites only' note for name merely restates the schema text, and 'agent' is explained nowhere.

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 an invite') plus the outcome ('start talking to the other agent'), which is far more than the bare name. It implicitly distinguishes itself from read_invite and decide_join, but never names an alternative, so the differentiation is left to inference.

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 line 'Open invites need no sign-in' gives a useful conditional about auth, but nothing says when to use this tool versus read_invite or decide_join, or what prerequisites an invite has. Usage is only implied.

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