Get vehicle forecast

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

With no annotations, the description carries the full behavioral disclosure burden, but it only says 'Get upcoming stops'. It does not clarify what 'upcoming' means in terms of time horizon, ordering, or real-time versus scheduled data, and it does not mention any limitations or side effects.

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 a single front-loaded sentence with no filler. It conveys the essential purpose immediately and earns its place without unnecessary detail.

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 simple one-parameter read tool, the description is minimally adequate, but it does not explain the expected output structure or the meaning of 'upcoming'. With no output schema and no annotations, slightly more context about time range or result ordering would make it more 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?

Schema description coverage is 100% and the schema already describes deviceCode as 'Vehicle device code from route vehicles.' The description repeats that the stops are for that device code but adds no new semantic detail beyond the schema.

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 states a specific verb ('Get') and resource ('upcoming stops') plus the input context ('for a vehicle device code'). This clearly differentiates it from sibling tools that operate on routes or stops rather than a vehicle device.

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 implies the tool is used when the caller has a vehicle device code and needs that vehicle's upcoming stops. However, it does not explicitly state when to use this tool over alternatives like get_route_vehicles or get_stop_arrivals, nor does it mention any exclusions.

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