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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety note at the end largely restates the closed-world annotation. The genuinely additive content is the UTC conversion rule (departure_at with departure_timezone, arrival_at with arrival_timezone), a real rendering behavior not captured by structured fields. Pagination and filter behavior ('Supports common list filters') remain unexplained.

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 type-slug list and its label mapping are stated twice (in the description and again in the schema), and the label mapping is low-value verbosity for an agent that already has the enum. Front-loading the resource scope is reasonable, but the timezone instruction and the safety note are tacked on without structure or headings.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. What is missing is the listing contract itself: required trip_id scoping, how filters combine, and the fact that this is the read counterpart to the create/update/show/delete siblings. The dangling reference to provider_reservation_code slightly undermines completeness by implying a parameter that the schema does not offer.

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%, so the schema already documents trip_id, fields, fields_exclude, deleted, updated_since, and activity_type; the description adds nothing for those. The transportation_type slug/label mapping is repeated verbatim from the schema's own enum description, so it is duplication rather than added meaning. The provider_reservation_code sentence references a field absent from the schema, which adds confusion rather than clarity.

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 opens with a noun phrase ('Flights, trains, cars, buses, ferries, walks, and other point-to-point travel') that scopes the resource but never states a verb such as 'list' or 'retrieve'. 'Supports common list filters' is the only clue that this is a listing operation, and nothing distinguishes it from siblings like tripsy_transportations_show or tripsy_transportations_create.

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?

There is no when-to-use or when-not-to-use guidance, and no naming of alternatives (e.g., use tripsy_transportations_show for a single record, or tripsy_transportations_create to add one). The only directive sentence concerns provider_reservation_code, which is not even an input parameter, leaving routing between the seven transportation/trip siblings entirely to inference.

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