get_hotel_preferred_drivers

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

With no annotations, the description must carry the behavioral burden. It discloses that the tool returns all preferred drivers and that the results are sorted by driver score, making the read operation and ordering transparent. It does not detail return format or empty-list behavior, but these are minor for a straightforward read.

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 a single, concise sentence that fully conveys the purpose and sorting criteria. No wasted words or repetition.

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 tool with one parameter and no output schema, the description captures the essential behavior (retrieving all preferred drivers) and ordering. It does not mention potential empty results or response shape, but these are not critical for the tool's basic usage.

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 input schema only defines hotel_id as a required string with no description (0% coverage). The tool description mentions 'for a hotel' but does not explicitly explain that hotel_id is the hotel identifier or any expected format. The description should compensate more for the bare schema.

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 clearly states a specific action ('Get all preferred drivers'), a resource ('for a hotel'), and an additional qualifier ('sorted by driver score'). This distinguishes it from sibling tools like add_preferred_driver, remove_preferred_driver, and list_available_drivers.

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 description implies when to use the tool (when you need the list of preferred drivers for a given hotel) but does not explicitly mention alternatives or exclusion cases. It lacks guidance on how it differs from get_next_driver or list_available_drivers.

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