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

Beyond the read-only and open-world annotations, the description explains that the destination is resolved internally, coordinates are optional, results are one ordered page, and returns include prices, distances, IDs, and signed propertyRef values. It also clarifies that propertyRef can identify a home for later reference, which is important behavioral context.

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 purpose and key constraints are front-loaded and easy to scan. There is minor redundancy around propertyRef and the audience sentence is helpful but not strictly invocation-critical, keeping it just below maximally concise.

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?

For a read-only, open-world search with no output schema, the description covers the main requirements, filters, and return shape well. It still leaves some parameter behavior, especially pagination details and child/price/currency semantics, to the schema alone.

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?

The description adds useful meaning for required dates/adults, optional coordinates, housingType, sort, and propertyRef. However, with 16 parameters and only 31% schema description coverage, several parameters such as page, size, currency, childrenAges, and nightly price bounds remain unclarified beyond their names and types.

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," and names the resources: extended-stay hotels, motels, and furnished housing. It also distinguishes the scope from detail/offer siblings by focusing on discovery near a destination for work-travel assignments.

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 clearly states the intended context: work-travel lodging for travel nurses, construction crews, outage workers, and similar assignments. It does not explicitly name when to use this versus get_hotel_details, get_hotel_offers, or get_home_offers, so alternatives are left implicit.

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