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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description does add genuine domain context — that member/guest ids are the referents used by plans, lanes and to-dos, and that people in no lane follow the shared plan — but says nothing about failure behavior (unknown tripId) or result size.

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?

Two tight sentences that front-load the entity and its contents, with jargon (splits, lanes) defined inline rather than assumed. The trailing sentence about people in no lane is useful domain semantics rather than filler, though the noun-phrase framing makes it read more like a data glossary than a tool instruction.

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 need not enumerate return fields, and it correctly focuses on the domain relationships an agent cannot infer from the schema. Nothing critical is missing for a read-only single-entity fetch; only error handling for an invalid tripId is unaddressed, which is minor.

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%: tripId is typed as uuid with a format pattern and documented as coming from list_trips. The description adds no parameter-level information beyond that, so the baseline 3 applies — the schema, not the prose, does the work here.

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 names the resource's distinctive contents — people (members and guests) and splits with lanes — which lets an agent distinguish it from get_plan, get_lists and list_trips, whose scopes are different slices of the same trip. It never states a verb ('retrieves a single trip by id'); the read intent is carried by the name and title rather than the description text.

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 is only implied: one required tripId and the notion of getting one trip's detail vs the list_trips enumeration the schema points at. There is no explicit 'use this when you need X' or 'do not use this for Y', and no sibling is named in the description even though list_trips, get_plan and get_lists overlap conceptually.

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