get_liveboard

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

No annotations are provided, so the description carries full burden. It discloses real-time nature and departure/arrival based on 'arrival' parameter, but omits details like authentication needs, rate limits, error handling, or response structure. The lack of transparency is significant for a data retrieval tool.

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 sentence with no filler, instantly conveying the core functionality. It is appropriately sized for the tool's simplicity.

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?

Despite high schema coverage and no output schema, the description lacks essential details for an agent: no mention of response format (e.g., list of departures with times, platforms), no error handling, no pagination. The tool has 5 parameters but the description provides no usage completement beyond what's in schema.

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%, so the schema already documents all parameters (station, date, time, arrival, lang) with clear meanings. The description adds no extra semantic value beyond stating 'departures or arrivals', which is already covered by the 'arrival' parameter description.

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 the tool retrieves real-time departures or arrivals from a station, using specific verb 'Get' and resource 'liveboard'. This distinguishes it from siblings like 'find_connections' (routes between stations) or 'get_train_info' (specific train details).

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 usage for real-time station data but does not explicitly state when to use this tool versus alternatives like 'find_connections'. No when-not-to-use or context provided, leaving the agent to infer from sibling names.

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