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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds genuinely useful provenance: Wikipedia airport articles, OpenStreetMap rail lines, Wikivoyage 'Get in/Get around', hand-assembled transit data 'with its sources and the day it was checked', and affiliate marking with disclosure. That freshness and sourcing context is real value beyond annotations.

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?

Essentially one enormous semicolon-chained sentence with parenthetical nesting, far past the point of readability. Content is not front-loaded into scannable segments; the agent must wade through clauses to find the key constraints. The information is present but the structure actively impedes use.

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?

There is no output schema, and the description compensates by enumerating what comes back (routes, airlines, distances, flight time, airports, transit cards, apps, ferries, map links). Missing details like freshness guarantees or result shape are minor for a read-only lookup. Coverage is strong for a tool of this complexity.

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 100% with only two parameters, so the schema carries the semantics. The description adds only that a non-departure city still works and that country inputs resolve to the most-visited place — marginal but non-zero added meaning. Baseline 3 is appropriate.

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 opening clause gives a specific verb+resource ('How to get from one of TravelCharika's departure cities to a place') and then enumerates the concrete content types (airlines, flight time, airports, getting around). The purpose is discernible and clearly distinct from siblings, but the run-on structure forces the agent to parse a single sprawling sentence to extract it.

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?

It explicitly excludes the flight-search use case ('No timetable and no prices: the flight searches in booking_links find the day's flights'), routing that need to a named sibling. It also handles the edge case of a non-departure city ('the place's own side and the departure cities nearest it'). No guidance on use vs. activities or where_to_go, but the primary alternative is named.

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