Koleo MCP Server

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

No annotations are provided, so the description carries the full burden. The verb 'Get' implies a read-only operation, but the description doesn't explicitly confirm safety, idempotency, error conditions, or rate limiting. Minimal behavioral disclosure beyond the action itself.

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, tightly constructed sentence with zero redundancy. Front-loaded with the action verb immediately establishing the tool's function. Every word earns its place.

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?

Adequate for a single-parameter lookup tool with an output schema (which handles return value documentation). However, lacks prerequisite guidance on how to obtain the 'internal Koleo ID,' leaving a gap for agents attempting to use this tool without prior context.

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?

Despite 0% schema description coverage, the description successfully compensates by explaining that the parameter represents an 'internal Koleo ID.' This adds critical semantic meaning missing from the schema. Could be improved by explaining how to obtain this ID or its format constraints.

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 ('Get') and resource ('train's route and stops'), and distinguishes from siblings by specifying the required identifier type ('internal Koleo ID'). However, it doesn't clarify the relationship to sibling 'tool_get_train_route', which appears to have overlapping functionality.

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?

Provides implicit guidance by specifying the tool requires an 'internal Koleo ID,' suggesting use when that specific identifier is available. Lacks explicit when-to-use/when-not-to-use guidance or comparison to alternatives like 'tool_get_train_route' or 'tool_search_connections'.

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