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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the required auth scope (read:room), which is genuinely useful operational context not present in structured fields. It does not mention pagination or ordering, but for a small read-only list tool that is a minor omission.

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?

A single sentence plus a short scope note; the resource and returned fields are front-loaded and every clause carries information. No 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 no input parameters and no output schema, the description usefully compensates by enumerating the fields returned and the required scope. Only pagination/ordering behavior and the relation to sibling list tools are left unaddressed, which is a small gap for such a simple tool.

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, so there is nothing to disambiguate and the baseline is 4. The description correctly implies a property-wide, unfiltered listing with no arguments.

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 ('List') and resource ('rooms of the property') and enumerates the returned fields (name, description, room type, active flag), so the agent knows exactly what it gets back. It does not explicitly contrast itself with the sibling thinkreservations_list_room_types, leaving the rooms-vs-room-types distinction to inference.

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?

The prerequisite 'Needs scope read:room' is stated, which is real guidance for callers. However, there is no explicit when-to-use/when-not guidance and no mention of the obvious alternative (list_room_types) or of how to follow up once room identifiers are needed.

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