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

The description adds meaningful behavioral context beyond the annotations by stating what each invite kind does: who becomes a contact, one-time club join, and one-to-one pairing. It does not cover the 'open' kind's behavior, and it does not disclose side effects like whether invites can be revoked or what happens on max_uses exhaustion.

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?

The description is compact and front-loaded: the first sentence states the operation, and the following clauses succinctly define each kind. Every sentence earns its place, and there is no redundant 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 main parameter 'kind' accepts four enum values, but neither the description nor the schema explains what 'open' does. Since this is a create/mutation tool with no output schema and the missing value could lead to incorrect use, this is a meaningful completeness gap.

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?

The schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds the default value for kind and restates the kind semantics, but it adds little meaning beyond what the schema's kind description already provides.

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 uses a clear verb and resource ('Create an invite') and explains the three main kinds with their distinct effects, so an agent can tell it apart from sibling tools like accept_invite or request_connect. It loses a point because it never mentions the 'open' kind, which is a valid value in 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?

The kind breakdown gives implied usage context: share for reusable contact-creating codes, network for one-time club joins, and pair for one-to-one pairing. However, it does not explicitly state when to use this tool versus related alternatives, nor does it provide any exclusions or prerequisites.

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