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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context beyond annotations by specifying the concrete scope ('all') and the exact result contents: descriptions and total lounge counts. This gives the agent a clearer expectation of what the call returns.

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 focused sentence front-loads the verb and object, then adds the key output fields. No filler or repetition, and every clause adds useful information.

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 zero-parameter list tool with strong annotations, the description is complete: it names the result category, the known members, and the included fields. There is no output schema, but the description effectively communicates what the response will contain.

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 schema coverage is trivially complete. With no parameters to document, the description does not need to add parameter-level meaning, and the 0-parameter baseline of 4 applies.

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 ('List') and a clear resource ('lounge networks'), and enumerates the exact networks (Priority Pass, LoungeKey, DragonPass, Plaza Premium, Amex Centurion). This differentiates it from siblings like get_network_lounges, which focus on lounges within a network rather than the network catalog 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?

The description clearly implies that this is the tool to use for a full catalog of lounge networks and their counts, but it does not explicitly state when not to use it or name alternative tools. An agent could infer the use case, but there is no direct routing guidance relative to siblings like get_network_lounges or find_lounges_by_access.

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