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

Annotations only declare this a safe read; the description adds real behavior the annotations cannot: date-less calls pick a weekend based on observed prices with per-person and total fares, dated calls quote no price, and the page surfaces a warning explaining why fares are poor and what to do instead. It also states the user should pass the warning on, which is genuine operational context. It does not contradict readOnlyHint or openWorldHint=false.

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?

It is front-loaded and appropriately short for a 5-parameter tool, but the prose is garbled in places ("the weekend whose round trips we have seen price everyone", "each person's cheapest fare we have seen for them or the closest"), which forces re-reading. The final clause about the warning is useful but tacked on with a colon-and-imperative that reads awkwardly.

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 an output schema present, the description did not need to detail return values, yet it covers the non-obvious branch between dated and undated calls and the warning banner. For a tool with nested members, an enum-less mode string, and a two-mode date behavior, this is close to complete; it only lacks any hint about link validity or sharing semantics.

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 coverage is already 100%, so the baseline is 3, but the description adds date-conditional meaning the schema cannot express: omitting out/back yields a suggested long weekend, supplying dates yields no quoted price. It also clarifies that the returned page lists each person's cheapest seen fare or the closest alternative, which frames what members/out/back actually drive.

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 the concrete product — "a link to a2bflight.com's group page for people flying from different homes to meet in one place" — so the agent knows it produces a shareable group-trip URL rather than fares or airport data. It differentiates itself from where_to_meet by naming that sibling directly, though the verb ("returns/creates a link") is implied rather than stated.

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?

It gives an explicit routing rule: use this when the user already knows the destination, and use where_to_meet when they are asking where to meet. That names both the condition for this tool and the alternative that selects against it, leaving nothing to inference.

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