search_intercity

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

No annotations provided, but description discloses return contents (times, duration, stops, fares), rendering method (headless browser, ~5-10s latency), and behavior for empty lists. No mention of auth or rate limits, but acceptable for a search 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?

Two well-structured paragraphs. First paragraph states purpose and scope, second lists parameters and return values. No redundant sentences; each sentence adds value.

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, but description explains return fields (departure/arrival time, duration, stops, Economy + Business fares in SAR) and edge cases like empty list meaning. Complete for a search tool.

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 has 0% description coverage, but the description adds examples and format for each parameter: 'Origin name or code (e.g. "Riyadh", "RYD", "Dammam")' and 'ISO format YYYY-MM-DD'. This compensates well.

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 'Search SAR intercity trains (East + North lines) WITH fares on a date.' It specifies the exact routes covered and distinguishes from the sibling tool 'search_trains' which is for the Haramain line.

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?

Explicitly says 'Use this instead of search_trains for any route NOT on the Makkah-Madinah Haramain line.' Also explains when to expect empty results (e.g., North line currently no bookable service).

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