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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the return payload shape (names, emails, roles, segment assignments), which is modest extra context, but says nothing about ordering, pagination, or behavior when trip_id is unknown.

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 sentences, front-loaded with the purpose and followed by the return contents; nothing is padded or repetitive. The second sentence is arguably redundant given the output schema, which keeps this just short of a 5.

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?

For a single-parameter read tool with an output schema and full annotation coverage, the description is nearly sufficient: the agent knows what it does and what comes back, and the output schema handles return structure. The only real omission is guidance on when to prefer this over known_participants.

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?

There is only one parameter and the schema documents it at 100% coverage with a clear description ('unique identifier of the trip'). The description's phrase 'for a specific trip' merely restates the schema, adding no format, sourcing, or validation detail beyond it.

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?

States a specific verb ('Get the list of') and resource ('travelers/participants') and scopes it to a specific trip, which is clear enough to act on. However, it never names the adjacent 'known_participants' or 'trips_hub' siblings, so an agent must infer the boundary between trip-scoped and global participant lookups.

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?

The description gives no when-to-use guidance, no exclusions, and no alternatives. With sibling tools like known_participants, traveler_add, and traveler_assign in the same namespace, an explicit routing statement (e.g., 'use known_participants for the account-wide list') would be needed to lift this above no-guidance.

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