trip_item_listList items for a trip with optional filters
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by type | |
| status | No | Filter by status | |
| tripId | Yes | Trip ID | |
| endDate | No | Filter to date | |
| startDate | No | Filter from date |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and destructiveHint annotations already establish that this is a safe read operation, and the description adds no behavior beyond what the schema already shows ('optional filters' is visible in the parameters). It does not disclose sorting, pagination, default filter behavior, or what the list returns, so no meaningful behavioral context is added beyond the structured fields.
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?
A single front-loaded sentence with no filler: the resource and action come first, and 'optional filters' is the only additional context. Every word eins its place, and there is no redundant prose.
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 is minimally viable for a safe, read-only list operation with fully documented parameters, but gaps remain: there is no output schema to describe the returned item shape, no mention of ordering/pagination, and the description doesn't disambiguate 'items' from the closely related sibling list tools. It is adequate but not complete.
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 input schema covers 100% of parameters with descriptions and enums, so the schema carries the semantic burden. The description only restates 'optional filters' generically and adds no parameteer-level meaning beyond the schema; therefore it meets the high-coverage baseline but does not exceed 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 clear action ('List') on a specific resource ('items for a trip') and notes optional filters. It is not vague or tautological, but it does not explicitly differentiate trip items from sibling list tools like trip_activity_list or trip_note_list, so it misses full sibling differentiation.
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?
Provides no guidance on when to choose this tool over alternatives, and no exclusions or context. With multiple sibling list tools (trip_activity_list, trip_task_list, trip_note_list), an agent must infer from the name alone; the description doesn't clarify use cases or boundaries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly separated by resource type and action, making selection. The main ambiguity is between trip_item_add and trip_transport_add, since trip_item_add lists transport as a category but trip_transport_add explicitly says to always use it instead for transport.
The naming pattern is highly consistent: trip_<resource>_<action>. Minor deviations exist with bare verbs like search and fetch, and trip_review uses a verb-only style, but these are easy to understand within the larger pattern.
37 tools is a large surface that exceeds the typical coherence threshold. While the domain is broad, the count makes the server feel heavy and harder for an agent to navigate compared to a more focused toolset.
The toolset provides strong CRUD/lifecycle coverage across trips, items, notes, tasks, locations, collaborators, shares, and transport, plus review and search capabilities. Minor gaps exist, such as no direct collaborator add, no location update, and no item-level comment delete, but these are workable.