List properties

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

No annotations are provided, so the description carries the full burden. It discloses the 'Local lookup — no API call' behavior, which is an important trait (no network latency, likely cached). However, it does not describe the exact return structure or whether the list is sorted/filterable, which for a zero-parameter list tool is a minor gap.

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 description is two concise sentences, front-loaded with the main action. It avoids wasted words and includes the usage cue in the second sentence.

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 stateless, zero-parameter lookup tool with no output schema, the description covers the essential points: what it lists (hotels and codes), when to call it (first, when code unknown), and a key behavioral trait (local lookup). This is complete given the tool's simplicity.

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 0 parameters, and the schema coverage is 100%. The baseline for zero-param tools is 4, and the description does not need to explain parameters. It adds value by clarifying the output includes property codes, but that's not parameter semantics.

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 explicitly states 'List all known hotels with their WebHotelier property codes,' using a specific verb and resource. It also differentiates from sibling tools (get_rates, get_availability) by focusing on the property registry rather than pricing or availability data.

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?

It gives clear guidance: 'Call this first whenever you don't know a property code,' which tells the agent when to invoke this tool. The additional note 'Local lookup — no API call' provides context that it is a fast, prerequisite lookup.

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