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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description adds real behavioral context on top: owner-only authorization, the fact that revoked invitations are deleted and therefore absent from results, and an output-presentation rule (never show IDs). Missing details on pagination metadata or response shape keep it from the top band, but the added context exceeds annotation restatement.

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?

Purpose and scope are front-loaded in the opening sentence, and nearly every clause carries semantics an agent needs (invitation states, link activity, per-trip vs account switches). The middle section is heavily parenthetical and nested, which costs readability but the density is largely justified by the tool's complexity.

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 and five optional parameters, the description must carry the return-value burden, and it does: it enumerates the three sharing mechanisms, invitation states, the public-link flag, friend-sharing switches, and the planVisibleVia values. Authorisation and data-lifecycle caveats are also present.

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 100%, so the baseline is 3; the description still adds meaning by noting trip_id omission triggers paging across all owned trips and by explaining that friend_user_id (sourced from friends_list) unlocks per-friend state including the derived planVisibleVia semantics. That is genuine value beyond the schema text.

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 first sentence gives a specific verb (read) plus resource (trip sharing) and immediately scopes the two modes: single trip via trip_id or all owned trips via paging. It is distinguishable from trip_sharing_set, which is named as the mutation counterpart.

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?

States clearly when to call it ("before trip_sharing_set and to report sharing status") and names the prerequisite source for friend_user_id (friends_list). It also flags the owner-only restriction, though it offers no explicit when-not or alternative read path.

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