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

With no annotations, the description carries the full burden and does substantial work: single-use, email-bound, token returned only once, no email is sent, and prior unused invitations for the email are replaced (a destructive side effect). It omits permission/auth mechanics and rate limits, but the side-effect profile is unusually well disclosed.

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, front-loaded sentences with zero filler; the audience restriction and the key behavioral facts each get exactly one clause.

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 mutation tool with no output schema, the description covers the important return behavior (token returned once) and the destructive replacement of prior invitations. The gap is the undocumented expiresInDays parameter and no mention of expiry implications.

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 description must compensate. It conveys the semantics of the email parameter only indirectly ('email-bound'), and says nothing at all about expiresInDays, its default of 7, or its 1-30 day range.

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 (issue), a specific resource (email-bound, single-use private invitation), and a scope restriction (platform operators only). This is clearly distinguishable from siblings like members_invite, invitations_list, and invitations_revoke.

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 prerequisite (platform operators only) and implies the use case via 'share privately' and 'does not send email', but never names an alternative or states when NOT to use it versus members_invite or members_invite's email-sending flow. Usage is inferable but not explicit.

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