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

Annotations already declare destructiveHint, idempotentHint, readOnlyHint=false and openWorldHint=false, so the safety profile is pre-supplied. The description adds genuine value beyond them by clarifying that only supplied fields are overwritten and that prior values are not automatically preserved or restored, which tells the agent this is a partial-patch semantic rather than a full replace.

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 purpose sentence is well front-loaded, but the twelve-slug list plus label mapping occupies most of the description and duplicates content the schema already carries twice. Roughly half the text earns no place.

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 and annotations cover safety, so the description only needed to establish scope and mutation semantics, which it does. Minor gaps remain around error behavior for an unknown id and whether trip_id must match the record's current trip.

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 description's slug/label table is a verbatim restatement of what already appears in both the data object description and the transportation_type property. No additional meaning is added for id, trip_id, or the arbitrary additionalProperties of the data object.

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 and resource ('Update a Tripsy transportation by id'), which is unambiguous against the create/delete/list/show/update sibling set. It does not explicitly name the sibling it replaces, but the verb+resource pairing makes selection obvious.

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 by the verb 'update' and the required id/trip_id pair. There is no statement of when to prefer this over tripsy_transportations_create (new record) or how to first locate the id via tripsy_transportations_list/show, and no exclusion guidance.

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