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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds real context beyond that: it enumerates what the card contains (reservation status counts for next 7 days, room/room-type/room-status/housekeeping counts), notes these come from bounded samples, and explicitly excludes guest, stay and payment data — useful privacy/scope disclosure.

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 that are tightly ordered: usage trigger, then return contents, then exclusion. No filler or redundancy, and the most decision-relevant information (when to use) is front-loaded.

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 single-parameter read tool with rich annotations and an existing output schema, the description supplies everything else an agent needs: what it returns, the bounded-sample caveat, and what data is deliberately absent. Nothing material is missing.

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?

Single parameter with 100% schema description coverage (pattern and format already documented in the schema). The description adds no syntax or constraint detail for hotelId, so the schema does all the work — baseline 3.

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 ('Show') plus the resource ('hotel operations overview' / dashboard) and constrains scope to one hotel. It also names the adjacent-but-different case ('Not for a single reservation'), letting an agent separate it from get_hotel and get_hotel_schedule_summary.

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 a clear triggering condition ('when someone wants a quick overview or dashboard of one hotel's operations') and one explicit exclusion ('Not for a single reservation'). It stops short of naming which sibling to use instead for detail or schedule, so it is strong but not fully routing.

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