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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower; the description still adds real value by disclosing data provenance (city trip records, Uber/Lyft vs. taxi meter rates) and what the answer contains. It stops short of stating freshness/coverage limits of the underlying records.

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?

Three sentences, front-loaded with the core question, then the data basis, then city fallback behavior. Every sentence carries information, though the opening sentence restates the title verbatim, costing a little space.

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, the description usefully sketches the return content (cheapest and most expensive hours today, whether waiting saves money) and covers the NYC/non-NYC split that governs behavior. It is close to complete, though it omits what the tool returns for non-NYC cities and any data-freshness caveat.

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%, so city, when, and miles are already fully documented, and the baseline is 3. The description adds only marginal context by explaining why results differ by city, but it does not clarify parameter interactions (e.g., how 'when' affects the per-hour comparison) beyond the schema.

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 specific question the tool answers ('cheapest time of day to take a ride') and separates two data regimes: NYC Uber/Lyft trip records vs. other cities' taxi meter rates. An agent can distinguish it from fare-estimation siblings, but the description never names or contrasts those siblings explicitly.

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?

Usage is implied through scope conditions ('For New York... For other cities...'), which tells the agent when the NYC-specific behavior applies. However, there is no explicit guidance on when to pick this tool over check_fare, estimate_fare, or get_taxi_tariff, and no exclusions are stated.

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