get_hotel_distance_and_transit

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, which cover the safety profile. The description adds no extra behavioral context such as network dependencies, approximations, or side effects. It does not contradict the annotations, but the description contributes minimal additional transparency beyond the structured data.

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 exceedingly concise: two sentences, zero redundancy. It front-loads the purpose and then notes the alias. Every word earns its place, and it is easy to scan.

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?

Despite having an output schema (which means return format need not be described), the tool has 5 parameters with no schema descriptions. The description omits critical parameter semantics and does not point the user to the alias for more details. An agent would likely need to inspect the alias tool or guess, so the definition is incomplete for self-contained use.

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?

With 0% schema description coverage, the description must compensate by explaining parameter meanings. It hints that 'origin' is likely a hotel and 'destination' is a target, which is useful, but it does not clarify the format of values, the role of 'country', 'provider', or 'travel_mode', or acceptable values. This leaves agents guessing on many parameters.

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 states a specific verb ('Calculate'), resource ('travel distance and transit options'), and context ('between a hotel and a target destination'), which is clear and unambiguous. It distinguishes itself from sibling tools by naming the hotel use-case, though it does not explicitly contrast with get_transit_and_directions beyond being an alias.

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?

No guidance is provided about when to use this tool versus the alias get_transit_and_directions or other navigation tools. The alias note implies interchangeability but does not explain any preference or conditional use cases. There are no exclusions or alternative recommendations.

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