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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered structurally. The description adds useful context about what the read returns (room types, check-in/out times, contacts), but it says nothing about auth requirements, rate limits, or failure modes and offers no pagination/granularity caveats.

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, with the capability statement front-loaded and the sibling redirect placed last where it is most actionable. Every clause earns its place.

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 and no parameters, the description must carry the return-value burden, and it does so partially by naming three data categories. It stops short of describing the response shape or whether all hotels are returned, so it is complete enough to call but not fully self-contained.

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 and has an empty schema with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies; the roomId mention is a return-value convention rather than a parameter, so it does not raise the score further.

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 (Fetch) and resource (hotel operational data from the WBE system), then enumerates the content returned: room types with roomId abbreviation codes, check-in/out times, and contact information. It also explicitly distinguishes itself from the sibling get_fact_sheet, so an agent can route without opening either 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?

Gives an explicit alternative and the condition that selects it: 'For rich marketing descriptions, use get_fact_sheet instead.' This covers the most likely confusion with the sibling tool, but it offers no guidance relative to the other siblings (search_availability, get_price_quote), so it is clear context rather than a full when/when-not map.

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