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

Goes well beyond the readOnlyHint/openWorldHint annotations: it names the awaiting_first_price and no_rates states and explains what each means (sold out/not open, re-checked daily), explains what report_url/csv_url are for (price-guarantee evidence, refunds, check-in negotiation), and warns that seasonality is on a separate scale from the tracked prices.

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?

The core return payload is front-loaded in the first sentence, but the description runs long and dense, packing fallback states, URL purposes and seasonality caveats into an undifferentiated block. For a two-parameter read tool with a fully documented schema, some of this prose is surplus rather than load-bearing.

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, so the description carries the full burden of describing returns, and it does so thoroughly — shape of the price series, the booking_guidance signal and its components, generated headline/summary text, export URLs, optional seasonality, and degraded states. An agent has everything needed to call and interpret it.

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%, so both parameters are already documented in the schema and the baseline is 3. The description adds only marginal meaning beyond that — it says language governs booking_guidance text and track_page_url, which the schema already states, and adds no format or sourcing detail for tracking_id.

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 and resource ('Return the recorded prices for one tracking') and immediately scopes what is returned (current, first, lowest, highest, change, trend, time series). The tracked-record scope distinguishes it implicitly from siblings like get_current_price and get_hotel_price_calendar without needing to name them.

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 by the description of the tracked-record scope and the awaiting_first_price / no_rates states, which tell the agent when results are meaningful. However, it never explicitly says when to choose this over get_current_price or get_hotel_price_calendar, and there are no stated exclusions or prerequisites beyond the tracking_id origin in the schema.

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