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

Annotations declare destructive=false, idempotent=true, openWorldHint=false, but readOnlyHint=false despite a 'get' verb. The description adds real behavioral context beyond the annotations: no message is sent, the link is a bearer credential ('Anyone with the link can join'), it carries referral attribution, and it is organizer-restricted. That is substantial, but the readOnlyHint=false ambiguity is left unexplained (e.g., whether link generation/rotation is a side effect).

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?

Front-loaded with the core action, then layered with security and referral semantics. Four short sentences with little waste; '(by text, email, etc.)' is the only genuinely optional phrasing.

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 behavior, authorization model, and sharing semantics are well covered for a single-parameter tool with no output schema. The main omission is the return shape, e.g., whether the response is a URL string or an object, which an agent must guess.

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?

One required parameter with 0% schema description coverage, so the description carries the burden. It implies group_id identifies the group the caller organizes and that organization is a precondition, but it never states the expected identifier form or what happens with a non-owned group id.

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?

Specific verb ('Gets') plus a precise resource ('the invite link for a wishlist group or Secret Santa'), and it scopes who can obtain it ('Only the group's organizer'). It does not explicitly contrast with the sibling get_wishlist_share_link, so an agent must infer that this is group-scoped while the other is wishlist-scoped.

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?

Clear usage context: call this when the organizer wants a link to share themselves, and the caveat that nothing is automatically sent tells the agent it must not assume delivery. No explicit when-not-to-use or named alternative is given for the wishlist-vs-group distinction.

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