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

Beyond the readOnly/idempotent annotations, it discloses the ranking methodology (a published formula), the returned evidence types (points, awards, hotel class, verified facts, distance), and the editorial policy that there are no guest reviews, no prices, and no paid placements. That policy context is not derivable from annotations or schema.

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 purpose is front-loaded in the first sentence, followed by return shape, ranking policy, and the input constraint. Dense and mostly waste-free, though the quoted-example parentheticals and the 'Best means...' clause add some length.

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 annotations covering safety and an output schema covering response shape, the description still fills the important gaps: ranking basis, evidence provenance, editorial independence, and the at-least-one-input rule. An agent has everything needed to invoke it 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 coverage is 100%, so the baseline is 3, but the description adds a real constraint the schema does not express: at least one of place or need must be given (the schema lists no required parameters). It also clarifies that limit returns fewer hotels while the full list URL is still provided.

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 concrete verb and resource ('the published Journeyed best-of list') plus the two input modes (a place or a need across Los Angeles). It is clearly separable from siblings like search_hotels, hotels_near, and get_hotel.

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?

It tells the agent to supply a place or a need, with at least one required, and points to list_places for discovering covered places. It does not explicitly state when to prefer search_hotels or hotels_near over this tool, so no exclusion guidance is given.

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