hemmabo_search_properties

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

Disclosures go beyond annotations: states it's 'discovery only', warns against quoting final price from search alone, describes what parameters are combined as one filter, and explains that results drop properties below capacity or unavailable for the exact date range.

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?

Description is about 6-7 sentences, efficient and front-loaded with main purpose. Could be slightly more structured (e.g., bullet points for returns), but no unnecessary words. Minor improvement possible but well within acceptable range.

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?

Given the presence of an output schema (not shown but indicated), the description covers all necessary context: usage guidance, parameter relationships, behavioral constraints, and what outputs to expect. No gaps for a search tool with this complexity.

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% with descriptions for each parameter. The description adds context that parameters combine as a single filter and that results exclude properties below guest capacity or unavailable for the exact range, which is not in the schema. This extra information justifies a score above baseline 3.

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?

Clearly states the tool searches for vacation rental properties by location and dates. Distinguishes from siblings like hemmabo_search_availability and get_verified_stay_offer by specifying 'discovery only' and that it returns property details for browsing.

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?

Explicitly says when to use (user wants to find places to stay) and when not to use (already has propertyId or host domain). Provides clear parameter guidance (at least one of region/country, guests, checkIn/checkOut with ordering) and directs to call get_verified_stay_offer before final answer.

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