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

No annotations are provided, so the description carries the full burden and does so thoroughly: live real-time availability, price unit (euro cents), sort order, exact direct prices with no OTA markup, the 6 s per-tenant timeout with skipped tenants reported in errors, and explicit 'no authentication, no rate limit, no pagination' guarantees. It also discloses that listed_matches are public website/phone data and not bookable here.

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?

Dense but appropriately sized for a multi-mode, no-annotation tool; the core purpose is front-loaded before the workflow and constraints. Slightly bloated by marketing framing ('like Booking.com but machine-native') and some parenthetical restatement, but nearly every clause carries operational 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?

With no output schema, the description still explains the return shape (verified offers plus an appended listed_matches array) and how matches are ordered. Combined with the constraints, timeout behavior, and auth/rate-limit disclosures, an agent has everything needed to call this correctly.

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?

Schema description coverage is 100%, so the schema documents all five parameters and the baseline would be 3. The description adds meaning beyond the schema though: the YYYY-MM-DD format, the cross-field constraint checkin < checkout, the prohibition on past check-ins, the 30-night cap, and the euro-cents unit for budget/prices.

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 ('Search the WHOLE Adaga network ... for a stay') and immediately distinguishes the two result classes (verified, bookable offers vs. listed_matches that are NOT bookable). An agent can tell this apart from network_directory and network_book without opening any 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?

Provides an explicit ordered workflow (search → pick tenant_slug + room_id → network_book → hand payment instructions to human) and names the alternative tool with the condition that selects it ('Use network_directory instead when you need the full roster without stay dates'). Nothing is left to inference.

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