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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral signal that the data is 'live' status and enumerates what is returned, but says nothing about freshness/refresh cadence, auth scope, or failure behavior for a closed/invalid location.

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 tight sentences: the resource and its returned fields are front-loaded, and the endpoint is a compact trailing detail. No filler.

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 correctly compensates by naming the returned fields. It is nearly complete for a single-read tool, though it omits any note on units/format of the estimated wait or behavior when the location is not currently serving.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already carries the semantics; the baseline is 3. The description adds nothing about location_id format or where to obtain it beyond the {locationId} path placeholder.

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 resource and scope ('live status of one location') plus the concrete return fields (open/closed, waiting and serving counts, estimated wait) and the underlying endpoint. This distinguishes it from the sibling waitwhile_list_location_status, which covers many locations, without needing to open either schema.

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: the word 'live' suggests real-time polling versus the aggregated list endpoint, and 'one location' implies a known location_id. There is no explicit when-to-use/when-not guidance or named alternative (e.g., list_location_status for all locations, get_location for configuration).

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