get_unit_detailsFull specification for one product type/model: layouts, dimensions, what is included (appliances, furniture, smart home), community amenities, imagery links, and the availability band.
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes | A product id from search_inventory (e.g. "2-bedroom", "studio") or a model name (e.g. "Ocean Residence"). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the burden of behavioral disclosure. It clearly describes the returned specification content, but does not disclose edge behavior such as handling of invalid product ids, whether availability data is live/current, or whether the call is strictly read-only.
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 description is a single dense sentence that front-loads the purpose and then enumerates the return categories. Every phrase carries information, with no filler or redundant wording.
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 one-parameter lookup tool, the description plus schema cover what is returned and how to supply the argument. It could be more complete by explicitly contrasting with get_pricing_and_deposit_policy or clarifying the meaning of the availability band, but nothing essential is missing.
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 description coverage is 100%, and the schema already explains the product parameter well, including source and examples. The description adds no parameter-specific detail beyond the schema, so the baseline score of 3 is appropriate.
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 states a specific operation ('Full specification for one product type/model') and lists the exact content returned: layouts, dimensions, inclusions, amenities, imagery links, and availability band. This clearly distinguishes it from siblings like get_pricing_and_deposit_policy and search_inventory.
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 implies use for retrieving a full spec sheet for a specific home type, and the schema references products from search_inventory. However, it does not explicitly state when to prefer this tool over siblings, nor does it mention any exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct primary purpose: searching product types, getting detailed specs, viewing pricing/policy, and submitting an inquiry. Minor overlap exists between search_inventory's starting price and get_pricing_and_deposit_policy's price ranges, and availability appears in both search results and unit details, but these are different levels of detail.
All tool names follow a consistent verb_noun pattern: search_inventory, get_unit_details, get_pricing_and_deposit_policy, submit_inquiry. Retrieval operations use get_, search uses search_, and the action uses submit_. The long pricing tool name is verbose but still fits the pattern.
Four tools is well-scoped for an inventory and sales-inquiry server. Each tool covers a distinct part of the buyer journey: discover, inspect, understand pricing, and express interest, without redundant or unnecessary operations.
The tool set covers the main inventory browsing funnel: search, details, pricing, and inquiry submission. It does not expose exact unit counts or direct reservation, but those are intentionally externalized via the reserve link, so the surface is reasonably complete for its stated purpose.