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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the roster is deliberately omitted and requires a separate scope, and the response includes derived progress fields rather than raw data.

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?

Three tight clauses with the payload description front-loaded ahead of the exclusion note and the parameter recap. No filler sentences, though the trailing 'Params: id (uuid)' is redundant with the schema.

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 not be explained, yet the description still previews the payload. Combined with annotations covering safety and the explicit roster exclusion, an agent has everything needed to call this correctly.

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 0%, but there is only one parameter and the description restates it as 'id (uuid)', which duplicates the schema's format: uuid rather than adding meaning. There is little else to say about a single identifier, so this is adequate but not additive.

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?

Names a specific verb+resource (single trip's details) and enumerates the payload: stops, info cards, change log, derived progress (day X/Y, completed stops). This distinguishes it cleanly from list_my_trips and get_my_trip_ratings, which are its nearest siblings.

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?

Explicitly states what is excluded (participant list) and routes the agent to the alternative (list_trip_participants plus the trips:roster scope). It does not state when to prefer this over list_my_trips, but the single-trip-by-id framing makes that implicit.

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