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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description's contribution is content-level (it returns starting charge, per-mile rate, waiting rate, extras, flat fares, tipping custom, source), not behavioral - it says nothing about caching, freshness, or coverage gaps for unknown cities. Adequate but not additive.

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 sentences, front-loaded with the resource and then a compact enumeration of returned fields. The first sentence duplicates the title exactly, which is a minor waste, but the rest is efficient and free of filler.

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?

With no output schema, enumerating the tariff components (starting charge, rates, time-of-day tariffs, extras, flat fares, tipping, source) usefully tells the agent what comes back. Combined with a fully documented single parameter and complete annotations, this is close to sufficient; only the absence of sibling disambiguation and freshness/coverage notes holds it back.

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% and the single city parameter is well documented with examples and a pointer to list_cities. The description adds nothing about the parameter, so the baseline 3 applies; the schema carries the full burden.

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 names the resource precisely (a city's official taxi meter tariff) and enumerates the data it covers, so the agent knows what it will get. However, the first sentence is a verbatim repeat of the title with no verb, and nothing distinguishes this from siblings like check_fare or estimate_fare, which plausibly also return fare data.

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?

There is no when-to-use guidance at all: no statement of when to call this rather than check_fare, estimate_fare, or best_time_to_ride, and no prerequisites or conditions. The only implicit cue is the 'official source' phrasing, which hints at authoritative reference data rather than a live quote.

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