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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, and the description reinforces this with 'Changes nothing' and 'Only reads' – some overlap, but it adds genuine value by documenting the error path and the per-type payload contents (owner, ring time, riders, joinability). It stops short of describing idempotency or caching behavior explicitly, so a 4 rather than a 5.

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 a tight enumeration of resolved link types. The detail about return contents is justified because there is no output schema, but the sentence is long and slightly list-heavy; still, every clause earns its place.

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?

With no output schema, the description usefully documents what each link type yields and covers the error case. Combined with annotations covering safety and openWorld behavior, an agent has enough to invoke it correctly; only pagination/rate details are absent, which are not relevant here.

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 100% and the single parameter is already documented as 'The link, or the message it came in.' The description restates this dual-input semantics ('a link ... or a whole message with a link in it') but adds no format, length, or parsing constraints beyond the schema. Baseline 3 is appropriate.

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 (reads/identifies) and resource (a link or message containing one), then enumerates the exact types it resolves: LFG alarm, LFG invite with referral code, Partiful/Luma event. This clearly distinguishes it from siblings like join_alarm, use_invite_code, and get_invite_card without needing to open their schemas.

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?

Explicitly bounds the scope: 'Only reads; joining an alarm or using an invite code are separate steps,' routing the agent toward join_alarm and use_invite_code. It also states the failure condition ('Any other link returns an error'), so the agent knows when this tool is not the right choice.

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