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

The annotations indicate read-only and idempotent behavior, and the description does not contradict this. It adds a hint about the output fields (user ids, roles, profiles) but does not mention potential errors, rate limits, or other behavioral aspects. Since the tool is read-only, no side effects are expected, but the description could be clearer about the nature of the operation.

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 description is concise, consisting of two short sentences without unnecessary jargon or repetition. It efficiently conveys the purpose and a key use case, fitting within the typical length for tool descriptions.

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?

The description mentions the output fields (user ids, roles, profiles) but does not specify the structure (e.g., whether it's a list of objects) or any pagination or ordering. It also omits error scenarios or edge cases. For a simple listing tool, this may be sufficient, but it lacks full detail about the response format and limitations.

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?

The schema defines journey_id as a string but provides no description. The description does not explicitly explain what journey_id represents, though it is implied to be the identifier of the trip. There is no additional detail about format, constraints, or how to obtain it, leaving the parameter semantics under-specified.

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 clearly states that the tool lists who is on a trip, including user IDs, roles, and profiles. It also provides a specific use case for retrieving IDs needed by set_item_travellers, which adds some context. However, the phrasing is slightly vague ('who is on a trip' could be interpreted loosely) and could be more direct.

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 a specific scenario for using the tool (to get IDs for set_item_travellers) but does not explain when to choose this tool over other list tools like list_journeys or list_visas. It also lacks guidance on when not to use it, such as when only basic journey info is needed.

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