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

With no annotations, the description carries the full behavioral burden and does so: no authentication required, no rate limit, no pagination, complete directory returned in one response. It also discloses the critical downstream constraint that 'listed' establishments are NOT bookable here despite appearing in the roster, which prevents a costly misinterpretation.

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 definition is front-loaded, with the roster scope and tier semantics before the alternative-tool routing. However, the OTA-commission passage ('OTAs take 15-25% AND own the customer') is business/marketing framing that does not change how an agent invokes the tool and dilutes an otherwise dense, information-rich description.

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?

There is no output schema, so the description must describe the return payload, and it does: the tier field, its two possible values, and the fields available for listed entries (name, address, phone, official website). An agent has everything needed to call it and interpret the response without further documentation.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It does usefully explain that the returned slug is the key accepted by network_search and network_book, which is a value-level detail rather than a parameter one.

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 verb and resource ('List every establishment in the Adaga direct-booking network') and immediately scopes it against siblings by naming network_search as the date-aware alternative. The tier taxonomy ('verified' vs 'listed') further clarifies what kind of entries the tool returns, which an agent needs to interpret the result set.

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?

Explicitly states when to use this tool versus network_search ('use this tool when you need the full roster or an establishment's slug') and explains that network_search should be used when stay dates are known. It also names the downstream tools that consume the returned slug (network_search, network_book) and conditions the latter on verified tier.

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