agoda_homes_search

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

With no annotations, the description fully carries the transparency burden. It discloses the credential-free/public nature, the city_id precedence rule, the pre-filter limit semantics, the data source relationship to hotel search, and the promise of 'full listing detail' for each result. This goes well beyond the schema.

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?

Three sentences, each earning its place: the core purpose, the filtering/data-source behavior, and the input selection semantics. It is front-loaded and free of filler, being appropriately dense for a tool with no annotations and a non-trivial filtering mechanism.

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 lacking an output schema, the description provides a thorough mental model: what is returned, how results are filtered, how inputs interact, and what authentication is required. Combined with the fully documented schema parameters, the tool is well-specified for an agent to invoke correctly.

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 descriptions already document the precedence rule, the free-text resolution, the 1-indexed page, and the limit semantics. The description paraphrases these without adding new parameter-specific meaning, so the baseline of 3 applies.

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 uses a specific verb ('Search') plus a clear resource ('Agoda Homes & Apartments by city'). It distinguishes from sibling agoda_hotels_search by explicitly stating results are 'filtered to non-hotel accommodation types' and drawn from the same city search as hotel search.

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 gives clear usage context: it is the apartment/homes-focused counterpart to hotel search and explains the two input modes (city_id vs free-text city). It implies when to use this tool (when you need non-hotel listings) but does not explicitly name the alternative tool or state exclusion conditions.

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