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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds value by specifying the exact networks and the output fields (descriptions and total lounge counts), which is particularly helpful given there is no output schema. It goes beyond the annotations by detailing what the result contains.

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?

A single sentence that is front-loaded with the verb and resource, and lists the specific networks without any fluff. Every word earns its place; it is concise and well-structured.

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 simple read-only list tool with no parameters, the description is complete: it states the purpose, the scope, and the return contents. Annotations cover the safety profile, and no output schema exists, so the description's mention of descriptions and counts is sufficient.

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?

The tool has zero parameters, so the baseline is 4. The description correctly makes no parameter claims, and since there are no parameters, no further semantic addition is needed.

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 clearly states the verb 'List' with a specific resource 'lounge networks' and enumerates the exact networks (Priority Pass, LoungeKey, etc.) plus what is returned (descriptions and total lounge counts). This distinguishes it from sibling tools like lounge_get_network_lounges, which list lounges within a network, not the networks themselves.

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: an agent can infer to use this tool when it needs a list of lounge networks and their counts. However, there is no explicit guidance on when not to use it or alternatives (e.g., lounge_get_network_lounges for lounges in a network). The context is clear but lacks exclusions.

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