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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the exact pricing basis (total incl. taxes and fees, 2 adults, standard rate), that room type and breakfast are reported only when Agoda supplies them, that nothing is stored, and two operational constraints — a 30-minute cache and a shared daily budget for live lookups. That last pair is exactly the kind of rate-limit context an agent needs.

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?

Front-loads the core purpose and scope in the first sentence, then layers use case, output hints and caching. Three sentences, no filler, though the opening sentence is dense and the cache/budget detail could be tightened.

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 return-value burden and does so: it names the total with taxes and fees, room type, breakfast, and agoda_url as evidence. Combined with the read-only annotations and full schema coverage, an agent has everything needed to call and interpret this tool.

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 schema already documents all five parameters, including the currency list and the 'use the currency the booking was paid in' instruction. The description adds only the agoda_hotel_id provenance (search_hotels) and the fixed 2-adult/standard-rate context, which is useful framing but largely duplicative of 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?

States a specific verb (Read) and resource (Agoda price for one hotel and one stay) with the exact scope of the reading: whole-stay total with taxes/fees, 2 adults, standard rate. This clearly distinguishes it from get_price_history, get_hotel_price_calendar and track_hotel_price.

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?

Explicitly names the situation (after booking elsewhere to see whether Agoda is now cheaper) and the downstream consumer (check_refund_claim), plus the comparison use case. The 'one-time reading — nothing is tracked or stored' line implicitly rules out the tracking siblings, so the agent knows when this is the wrong tool.

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