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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value by disclosing the breadth of returned content, which matters because no output schema exists. It omits error behavior for an unknown slug and any rate-limit or auth notes.

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?

One sentence, front-loaded with the headline ('Everything about a lounge') and then a parenthetical inventory of fields. The list is long but each item is a distinct returned field, so it earns its place; a slightly tighter grouping would improve scanning.

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, enumerating returned content is exactly the right compensation, and it is thorough. The remaining gap is workflow context — how to obtain a slug and what happens when it is invalid — which matters for a lookup-by-identifier 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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description adds nothing about slug format or resolution — the 'search_lounges lists them' hint lives in the schema, not the description.

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 verb and resource — retrieve the complete record for a single lounge — and the enumerations (location, hours, guest policy, ratings, admitting programs, page links) make the scope concrete. It does not explicitly name or contrast with siblings such as get_lounge_metrics, search_lounges, or top_lounges, so an agent must infer the boundary.

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: 'Everything about a lounge' suggests fetching full detail for one known entity, and the schema note about slugs hints at a discovery flow. There is no explicit when-to-use, when-not-to-use, or 'use search_lounges first' routing in the description itself.

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