get_departures

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

No annotations provided; the description says 'live departures' but does not disclose whether delays, cancellations, or status details are included. No mention of rate limits, error handling, or required permissions for a read 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?

Single sentence, front-loaded with 'Get live departures'. Efficiently conveys core purpose, but could add more contextual detail without becoming verbose.

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?

No output schema, so description should hint at return format (e.g., list of departure times, lines, delays). It mentions transport modes but does not explain response structure. With siblings like search_journeys and get_arrivals, guidance on when to use this tool is missing.

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 coverage is 50%: stationId has a description in schema and the tool description adds 'from search_station tool' – helpful. Duration parameter has no description in schema or description, leaving its unit (minutes?) and behavior unclear. The description partially compensates for stationId but ignores duration.

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 'Get live departures for a station by ID', specifying the verb and resource. It lists transport modes (trains, buses, trams, etc.) but does not differentiate from the sibling tool 'get_arrivals' beyond the obvious verb difference.

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?

No guidance on when to use this tool over siblings like get_arrivals, get_disruptions, or search_journeys. It does not mention prerequisites or when not to use it.

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