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

Annotations already establish a safe idempotent read with no open-world access, so the bar is lower. The description still adds real behavioral value by disclosing that from_price_per_night_eur is mostly low-season and is not the actual stay price, pointing to price_terms and check_availability — a caveat an agent could not get from the annotations or schema.

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?

Two sentences, front-loaded with the purpose before the field enumeration, and every clause carries information an agent needs (returned fields, price caveat, routing). The long comma-separated field list is dense but earns its place; it could have been tightened slightly.

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 two-parameter read-only listing tool with a full schema and an output schema, this covers purpose, scope, key caveats, and hand-offs to siblings. Nothing critical is missing, though pagination/volume behavior on the unfiltered 'all houses' case is unmentioned.

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% and both enum parameters are documented there, so the baseline is 3. The description only restates the optional house filter and says nothing extra about language defaults or how house values map to results, adding no meaning beyond the schema.

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?

Opens with a specific verb and resource ("Lists the room types") plus the scope modifier ("optionally for one house"), then enumerates exactly what comes back (id, name, house, size, guests, features, booking mode, from-price, URL). It explicitly distinguishes itself from get_room (details) and check_availability (real stay price), so an agent can route without opening another 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?

Names both relevant alternatives with the condition that selects them: use get_room for details and check_availability for the real price of a stay, implying this tool is the overview/catalog step. The scoping rule ("optionally for one house", omit house for all) is also stated, leaving little to inference.

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