get_pricing_and_deposit_policyCurrent list price ranges per home type (USD), the refundable reservation deposit amount and its policy, the payment milestone schedule, and the link to reserve online.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral context. It indicates this is an informational retrieval tool through words like 'current' and by listing returned policy data, so calling it appears safe and side-effect-free. Still, it does not explicitly state read-only behavior, data freshness limitations, or any authentication requirements.
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, information-dense sentence that front-loads the most important output, price ranges, and then lists the remaining elements efficiently. There is no repetition, filler, or irrelevant detail.
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?
With no output schema and no parameters, the description fully carries the responsibility of explaining what the tool provides. It enumerates all major return elements: price ranges, deposit amount, policy, payment milestones, and reservation link. The tool is simple enough that this list is sufficient for an agent to understand the call's purpose and result.
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 tool has zero parameters, so there is no parameter semantics to document. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on the returned content rather than input details.
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 clearly states the resource: current list price ranges per home type, refundable reservation deposit amount and policy, payment milestone schedule, and online reservation link. It is not a tautology and is specific enough to suggest a distinct purpose, though it does not explicitly contrast with sibling tools.
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 when to use the tool: whenever pricing, deposit, payment schedule, or reservation link info is needed. However, there is no explicit guidance on when not to use it or which sibling tool to prefer, leaving the agent to infer selection from the content list and sibling names.
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.