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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and open-world nature are covered. The description adds a light note on result contents (property IDs plus listing URLs), but says nothing about pagination ceilings, result caps, or the fact that an unresolved city name triggers an extra destination-resolution lookup.

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 sentences, zero filler. The what/returns clause is front-loaded and the routing sentence follows immediately, so the highest-value information is read first.

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?

An output schema exists, so return values need not be re-explained, and annotations carry the safety profile. The description is adequate; only the city vs. city_id ambiguity and the optional-pagination behavior are left entirely to the schema, which handles them well.

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 100% and the schema already documents city, city_id, page, and limit with precedence rules and defaults, so the 3 baseline applies. The description's phrase "by numeric city ID" slightly undersells the free-text `city` path and implies a required city_id, adding no real meaning beyond the 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 names a specific verb and resource ("Search Agoda hotels"), states the primary key (city) and describes the payload ("matching property IDs with listing URLs"). It explicitly distinguishes itself from two Agoda siblings, agoda_hotel_detail and agoda_homes_search, so an agent can pick it without opening either 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?

It names both alternatives and the condition that selects them: agoda_hotel_detail when you already want a specific property, agoda_homes_search for vacation rentals, leaving this tool as the city-level discovery step. That is explicit routing rather than implied usage.

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