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

Annotations only cover the safety profile (readOnlyHint, openWorldHint=false), so the description usefully adds scope of data coverage, the upstream source, and the important limitation that pricing/availability are absent. It does not describe result ordering or how the limit interacts with a 1,000+ record directory, which would be the remaining 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?

Two dense sentences with zero filler; scope and coverage come first, then the critical limitation is placed last for emphasis. Nothing restates the name or title.

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 output schema, the description correctly compensates by enumerating the returned fields (name, type, sub-city, stars, phone, website, bina.et page). Combined with annotations it covers the safety and data-shape picture, though pagination/limit behavior and result ordering remain unstated.

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?

Schema coverage is 60%, and the description loosely maps to the parameters (type -> kind, sub-city -> area, stars -> min_stars), but the type list it names ('pensions', 'furnished apartments') does not match the enum values (motel, apartment), which risks misleading an agent picking a kind. The undocumented name/limit/min_stars params get no added semantics from the description.

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 resource (hotels, guest houses, pensions, hostels, furnished apartments in Addis Ababa), the data source (BinaSmart's directory, 1,000+ places from the city map), and the exact fields returned. It also carves itself apart from the rooms-oriented sibling get_hotel_rooms by declaring 'NO prices or free rooms', so an agent can disambiguate without opening a schema.

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 clear context for when to use it (directory lookups for lodging in Addis Ababa) and an explicit negative case plus fallback workflow ('NO prices or free rooms - tell the guest to call the hotel'). It stops short of naming the alternative tool (e.g. get_hotel_rooms) for availability, which would have made routing unambiguous.

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