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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuine context beyond them: the no-dates constraint, the strict ID-integrity rule (never shorten, combine or placeholder), and an explicit list of data that is not returned. These are real behavioral constraints an agent cannot infer 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?

The identifying behavior and usage rules are front-loaded in the first two sentences, and every clause carries an actionable constraint. It runs slightly long with some repetition of the ID-integrity warning that also appears in the schema, but nothing is filler.

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 an output schema present, the description does not need to explain return values and correctly focuses on identity resolution and scope boundaries. For a four-optional-parameter lookup tool, everything needed to call it correctly is stated.

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 100%, so parameter documentation is already strong and the baseline is 3. The description adds priority semantics between propertyId and hotelName, including when to prefer the fallback, which the schema hints at but does not fully rank.

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 ('Returns undated facts for one identified Brek property ID') and enumerates the payload fields (address, photos, amenities, check-in/out, rating, reviews). It also explicitly excludes availability, room offers, prices, breakfast and cancellation terms, which cleanly separates it from get_accommodation_offers.

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 concrete routing rules: copy the propertyId from a prior search_accommodations result when the user references a hotel by name or list position, fall back to hotelName plus optional destination when no ID exists, and ask for clarification if multiple hotels match. It also notes no stay dates are needed, so the agent knows when NOT to use it.

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