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

Annotations already declare readOnly/idempotent/non-destructive/no-open-world, so the safety profile is covered. The description contributes beyond that: what each result contains (straight-line distance, walking minutes, driving distance, sourced facts with source URL and checked date) and, importantly, the fallback behavior when no page covers the need there — it returns a message listing covered 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?

The first sentence front-loads purpose and scope, and the later sentences cover return fields and the no-page fallback without fat. The long parenthetical enumeration of needs largely duplicates the schema's need description, which is the one place it could be trimmed.

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 read-only lookup with a full output schema, the description covers the remaining gaps: single-need constraint, result contents, and the not-covered fallback. Return-value detail is slightly redundant given the output schema, and the absence of routing versus sibling hotel tools is the only real hole.

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 and the schema already lists the need vocabulary and limit bounds. The description adds the non-obvious semantic that only ONE need may be supplied at a time, and frames limit against the full-list URL, which the schema does not convey.

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 specific resource and scope: ranked hotels near a named Los Angeles place, optionally filtered by a single need. It is far more specific than a tautology and implies the curated 'journeyed.org page' model that differentiates it from search_hotels/best_hotels, but it never names those siblings, so an agent must infer the boundary itself.

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 rather than stated: have a place, optionally add one need, and use list_places to discover valid place names. There is no explicit when-not guidance and no routing against the sibling hotel tools (search_hotels, best_hotels, get_hotel), which is the main thing an agent needs to choose correctly.

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