Koleo MCP Server

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

With no annotations provided, the description carries full disclosure burden. It only adds the word 'upcoming' implying time-bounded results, but does not clarify the time window (e.g., next hour, 24 hours), pagination behavior, or what 'upcoming' means when a specific date is provided.

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 redundant words. However, given the complete lack of schema descriptions and absence of annotations, this brevity underserves the agent's information needs.

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?

While an output schema exists (covering return values), the description inadequately documents the two input parameters (0% schema coverage). Missing usage guidelines and behavioral details (scope of 'upcoming') leave significant gaps for a tool with multiple siblings.

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 0%, requiring the description to compensate. While 'from a station' implies the station parameter, the description does not specify whether 'station' expects a code, ID, or full name, nor does it mention the 'date' parameter's format or behavior when null.

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 clear action ('Get') and resource ('train departures') with scope ('upcoming'). However, it does not differentiate from siblings like 'tool_get_realtime_timetable' or 'tool_search_connections' which may also return departure information.

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 is provided on when to use this tool versus alternatives (e.g., 'tool_get_arrivals' or 'tool_search_connections'). The description also fails to explain when to provide the 'date' parameter versus omitting it.

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