Hammergut Neidberg – holiday apartments, Saxon Switzerland

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds real behavioral context: the return payload is enumerated field by field, prices are stated as exact, in EUR, including VAT, and the no-dates fallback behavior is disclosed — none of which is derivable from annotations.

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?

Three sentences, front-loaded with purpose and price semantics, then the return contract, then the edge case. No filler and nothing repeated from the schema.

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 does the work of describing returns and covers the date-less case well. The main remaining gap for an 8-parameter tool is that half the occupancy parameters are undocumented anywhere and the description does not compensate.

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 coverage is 63%, so the schema documents lang, adults, guests and the date patterns, while pets, children_3_6 and children_7_17 carry no descriptions at all. The description only indirectly touches parameters via 'Without dates', leaving the age-split vs. total-guests ambiguity and the pricing effect of pets unexplained.

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/resource pairing: live availability and exact prices (with currency and VAT treatment) for a stay, plus what is returned per unit. This is far more specific than the sibling names suggest (create_booking_request, get_property_info, list_accommodations), but the description never names a sibling or explicitly distinguishes itself from list_accommodations.

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 by 'for a stay' and by the fallback rule 'Without dates it returns the next free period per unit', which effectively signals the date parameters are optional. However, there is no guidance on which guest-count parameters to supply (guests vs. adults plus the two children buckets plus pets), and no stated when-not or alternative tool.

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

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

Adds substantial behavior beyond the annotations: no charge, immediate e-mail, a 15-minute confirmation link, and that the booking is only binding after the click (otherwise it expires). What it does not disclose is what the call returns (a request id?) or that the non-idempotent nature means retries risk duplicate requests — a real gap for a write tool with idempotentHint=false.

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?

Four tight sentences, front-loaded with what happens, then the eligibility gate, then the guest-facing instruction. No filler; each sentence carries a distinct constraint an agent must obey.

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?

The high-risk workflow (consent, expiry window, no charge) is well covered and no output schema exists, but the description says nothing about the response the agent needs to report back, nor warns about duplicate-submission risk for a non-idempotent create. For a 15-parameter mutation tool that leaves meaningful operational gaps.

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 only 27% across 15 parameters, so the description must compensate. It only implicitly touches unit_ids, checkin/checkout, adults and privacy_consent; the optional fields (pets, baby_cot, high_chair, bike_garage, children_0_2/3_6/7_17, guests_per_unit) and the nested guest object's required address fields are unaddressed in both places.

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 ('Creates a booking request ... for one or more units') and scopes the input by pointing at the sibling tools that supply unit ids (list_accommodations / check_availability). An agent can immediately distinguish this mutation tool from the three read-only siblings.

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?

Gives an explicit precondition gate: 'ONLY call this after the guest explicitly asked to book, confirmed unit, dates, guests and the total price, and agreed to the privacy policy.' It also names the follow-up action ('Tell the guest to check the inbox right away'), so both when-to-call and what-to-do-after are covered.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it discloses that the response includes policy-level facts (cancellation rules, tourist tax, how booking works) that an agent should absorb before mutating anything. It does not describe response shape, but the topic list largely substitutes for that.

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, zero filler. The subject (which property) is front-loaded, the content inventory follows, and the call-ordering instruction lands last where it is most actionable.

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 parameters, no output schema, and annotations covering safety, the description carries the remaining burden and does so: it tells the agent what topics come back, which is exactly what a missing output schema would otherwise leave unknown. Nothing needed to call this correctly is absent.

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 of 4 applies; there are no argument semantics to mis-specify. The description correctly makes no parameter claims, which is consistent with the empty 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?

The description names a specific resource — facts about Hammergut Neidberg in Saxon Switzerland — and enumerates the content domains (location, check-in/out, tourist tax, pets, payment, cancellation, booking process). An agent immediately knows this is the static-info tool rather than a booking or availability tool. It stops short of naming the siblings explicitly, keeping it at 4 rather than 5.

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?

'Call this first when planning a stay' gives a clear ordering rule that implicitly positions it ahead of check_availability and create_booking_request. There are no explicit exclusions ('do not use for X'), but for a zero-parameter info tool the context is unambiguous.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and closed-world scope are covered. The description adds genuinely new behavioral facts — the exact set is fixed at 5 units and amenity text is German — but does not say the result is unfiltered/unpaginated or whether it is static inventory.

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 tight sentence with the key fact (5 bookable units, composition) front-loaded before the field list. The parenthetical is dense but every element — unit count, breakdown, returned fields, German amenity text, photo URLs — carries information the agent would otherwise lack.

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 usefully enumerates the returned fields (capacity, bedrooms, beds, pets, amenities, photo URLs) and the language caveat. What remains unstated is call-ordering relative to check_availability/create_booking_request, which keeps it just short of complete.

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 there is nothing for the description to disambiguate; baseline 4 applies. It does implicitly confirm the call is parameterless by presenting a fixed catalogue.

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 names the resource precisely — the 5 bookable units (4 Hammergut apartments plus Waldhaus) — and enumerates the attributes returned. It omits an explicit verb like 'list/return', relying on the title and the '5 bookable units' framing to convey it is a full enumeration rather than a filtered query.

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?

No guidance on when to call this versus siblings such as get_property_info (single-unit detail) or check_availability. The agent must infer that this is the entry-point catalogue call, and nothing states that no filtering or date scoping is supported.

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