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

Annotations only supply readOnlyHint=true, but the description adds substantial behavioral context: shared trips have their charter and `pickupBase` withheld, `map` omits legs with no geometry, `get_share` returns a public no-login link or null, and `get` composes metadata rather than requiring separate crew/charter reads. These are real disclosure of data-visibility rules beyond the annotations.

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?

Every sentence carries information — action semantics, visibility rules, and data-type conventions — with no filler, and the action list is front-loaded. It is, however, one dense unbroken paragraph covering five actions plus output conventions, so structure could be improved.

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 does much of the return-value work (GeoJSON FeatureCollection shape, per-leg features, omitted geometry, null share link). It does not explain list pagination/ordering or result counts, a modest gap for a tool that has limit/offset parameters.

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 anyOf branches fully constrain each action, so the schema already carries parameter semantics; baseline 3 applies. The description reinforces the ID format ('6-character case-sensitive alphanumeric') but adds no meaning about limit/offset pagination behavior.

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 a precise verb+resource and then enumerates each of the five actions (list, list_shared, get, map, get_share) with what each returns, so an agent can tell them apart without opening the schema. It also preempts confusion by noting 'there is no separate crew or charter read' and distinguishes the caller's own log from trips shared with them.

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 explicit routing: `list` is the caller's OWN log, `list_shared` is for trips others shared, and a shared trip is 'readable with `get` and `map` and listed by `list_shared`, never by `list`'. The alternatives and the exclusion condition are both spelled out, 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.