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

Annotations already mark the tool as read-only, and the description goes far beyond that by detailing the computed booking_guidance fields, the seasonality caveat, the level-shift handling, and the awaiting_first_price edge state. This gives the agent a faithful model of what the tool returns and how it can behave.

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 description is long but front-loaded and well organized: core output first, then the booking signal, then URLs, then seasonality, then the edge case. Every sentence carries useful information, though some clauses are dense and could be tightened without losing 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?

With no output schema, the description carries the full burden of explaining the return payload, and it does so in detail: price stats, booking_guidance components, track_page_url, report_url/csv_url, seasonality semantics, and the awaiting_first_price state. This is sufficient for an agent to call and interpret the tool correctly.

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 the baseline is 3. The description largely repeats what the schema already states for tracking_id and language, adding no new param-level detail such as validation rules, additional formats, or default behaviors 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 opens with a specific verb and resource: 'Return the recorded prices for one tracking (tracking_id)'. It enumerates the exact outputs, making the tool's scope clear and distinct from siblings like list_tracked_hotels, track_hotel_price, and get_hotel_price_calendar.

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?

The description gives clear context that this tool is for retrieving a single tracking's full price history and supporting evidence artifacts. It even mentions practical use cases (best-price-guarantee claims, refund requests, check-in negotiation), but it does not explicitly name alternative tools or state when not to use this one.

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