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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds that the data is live and that an empty result is legitimate, which is useful but not rich enough to go beyond a 3.

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 short sentences, front-loaded with the method and resource. It is compact, but 'Live hotel rail' is jargon and does not earn much of its keep.

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?

An output schema exists and annotations cover the read-only/idempotent character, so return-value and safety documentation are handled. However, the description omits usage context and does not help an agent decide when the optional nonce/signature params apply, leaving it merely adequate.

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?

Every parameter already has a description in the schema (100% coverage), and the tool description adds no parameter-level meaning. Baseline 3 is appropriate because the schema carries the burden, not the description.

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 opens with the HTTP verb and resource ('GET /api/hotel') and defines the key semantic ('Occupancy is the guest count'), so an agent can tell this reads hotel occupancy. It does not explicitly name a sibling or say what a 'hotel rail' is, which keeps it from a 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?

There is no guidance about when to call this instead of sibling tools such as rooms_list, present_bed, or plaza_list. The description implies a live read but gives no exclusions or conditions, so an agent must infer the use case.

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