get_trip_stops

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

With no annotations, the description carries the burden of behavioral disclosure. The verb 'Get' and the stated return content imply a read-only retrieval, and the description says it returns all stops with arrival/departure times. However, it does not explicitly cover read-only safety, error behavior, timezone semantics, or data freshness.

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 front-loaded with the core action and is appropriately sized for a one-parameter retrieval tool. The trip ID source is repeated in both the usage line and the Args section, which is a minor redundancy but does not harm clarity.

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-value details need not be fully specified. The description still usefully states that the result contains all stops with arrival/departure times and documents the only parameter's source. It is nearly complete, with only minor gaps around edge cases and error behavior.

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 has one required parameter with 0% description coverage, so the description must compensate. It does so fully by naming the trip_id parameter, explaining it is a GTFS trip ID, providing an example format, and telling the agent where to find valid values in get_departures results.

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 and resource: getting the full schedule of a specific trip, including all stops and arrival/departure times. This distinguishes it from general stop or departure tools, though it does not explicitly contrast with siblings like get_route or get_departures beyond noting where trip IDs originate.

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?

Clearly says to use this tool to trace a vehicle along its route and see arrival times at each stop, and explains that trip IDs are found in get_departures output. It gives clear context but does not explicitly state when not to use it or contrast it with other route-planning siblings.

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