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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds that results are page links whose pages show review findings and an analysis date, but says nothing about result limits, pagination, or behavior on no-match.

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 short sentences, zero filler: the lookup and its inputs come first, the return shape second. Every clause earns its place.

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?

For a one-parameter read-only search with no output schema, the description covers what is searched and what comes back (links plus per-page content), which is nearly enough. Only external details like result caps or pagination are absent.

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% with a single self-documented param ('Hotel name or city'), so the schema carries the semantics. The description restates the same two search axes without adding format, length, or matching behavior, so the baseline 3 applies.

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 ('Find HotelShortlist research pages') plus the search axis ('by hotel name or city'), so an agent knows exactly what it retrieves. It does not distinguish itself from the sibling request_hotel_page, which is a plausible adjacent step, so it stops short of a 5.

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 only implied: the phrasing 'by hotel name or city' signals this is the entry-point lookup, and 'Returns page links' hints it precedes fetching a page, but neither the when-to-use nor any exclusion against request_hotel_page is stated.

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