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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating here. The description adds a genuine behavioral detail — that the address/coordinate data mirrors the house's Google profile, and that returned texts and links follow the language parameter. It says nothing about response shape, but an output schema exists, so that omission is acceptable.

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 subject and property are front-loaded and the closing routing sentences are efficient. However the middle is a long run-on inventory, and specific award counts ("Gault&Millau 4 toques, Falstaff 4 forks") and marketing content ("the Longboard Classic with its legends, and Glen Plake's quote") consume space without helping an agent decide or invoke.

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 zero-required-parameter, read-only fact lookup with full schema coverage and an output schema, the description covers the necessary ground: what content is returned, which house and language axes exist, and where to go for rooms or pricing. Nothing essential to correct invocation is missing, though the overlap with other informational siblings remains unaddressed.

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 parameters are enums with defaults, so the schema already fully documents them. The phrase "of each house" in the description hints at the per-house granularity of the returned facts but adds no syntax, default, or interaction detail beyond the schema. Baseline 3 applies.

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 specific resource (facts about Hotel Mondschein in Stuben am Arlberg) and enumerates the content families it returns: address/coordinates, contact channels, check-in/out, restaurant awards, opening hours, season. It also explicitly separates itself from list_rooms and check_availability, so an agent can place it among siblings. It stops short of a single crisp verb+resource statement because the opening is a content inventory rather than a summary of the operation.

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?

"Use for contact, address, directions and awards" gives an explicit use case, and two siblings are named with the conditions that select them (rooms, prices/dates). What is missing is routing against the other fact-like siblings such as get_faq, get_area, get_topic and list_houses, so the agent must still infer the boundary for general informational queries.

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