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

The description adds substantial behavioral context beyond the annotations: requires login and organizer role, the link itself is a secret key, repeated calls reuse the unexpired link and do not invalidate previously sent links, and non-public sessions will be rejected with the reason in the response. This is exactly the kind of disclosure that helps an agent invoke the tool safely and correctly.

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 well-structured with clear headers for login requirement, when to use, combination chain, and behavioral rules. It is dense but every sentence carries useful information, and the most important decision guidance is front-loaded. No filler or redundancy.

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 one-parameter tool with no output schema, the description covers almost everything needed: auth, use case, prerequisite check, security, idempotence, and rejection conditions. The only minor gap is that the success return payload is not explicitly described, though the description strongly implies a URL is returned. This is a small omission given the otherwise thorough context.

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?

There is only one parameter, activityRef, and the input schema already documents it as an activity slug or id with sources from list_my_activities and get_organizer_activity. Since schema description coverage is 100%, the description does not need to add much. It provides useful surrounding context about public events and reuse, but no additional parameter-level meaning.

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 states a clear verb and resource: create a self-recommendation link for external guests when no suitable internal candidate is found. It also distinguishes itself from get_activity_invites by saying to reuse an existing openInvite URL instead of recreating. This gives the agent a precise understanding of what the tool does and how it differs from related tools.

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?

Usage conditions are explicit: use when internal candidates are insufficient, and the link is meant to be forwarded to a group so people can self-nominate. It also gives a concrete combination chain: call get_activity_invites first, and if an openInvite already exists, use its URL rather than calling this tool. The restriction that only public events can create the link is clearly stated.

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