rentals.getReturn localized customer-safe apartment details, verified availability, duration pricing, deposit, included services, terms, eligibility, media, and inquiry/application links.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | de | |
| rentalId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | ||
| status | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the basic behavioral profile. The description adds context by noting the return includes 'verified availability' and 'customer-safe' details, implying safety and validation. However, it does not describe error behavior, such as what happens if the rental ID is invalid or the rental is unpublished.
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 sentence that efficiently lists the returned components. It is front-loaded with the main action. However, the enumeration of many items makes it somewhat dense, and a slight restructuring could improve readability without adding length.
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 simple input schema (2 parameters) and the presence of an output schema (not shown), the description provides adequate context for understanding the tool's output scope. It covers a wide range of returned fields. However, it omits details on error handling or edge cases, which would be useful for completeness.
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 0%, meaning the description adds no meaning beyond the schema. The schema defines 'rentalId' (required string) and 'locale' (enum, default 'de'), but the description does not explain their roles or provide any additional context. The agent must rely solely on schema definitions.
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 tool returns detailed rental information, listing specific aspects like availability, pricing, deposit, services, etc. The verb 'Return' and resource 'localized customer-safe apartment details' make the purpose unambiguous. It distinguishes from sibling tools such as 'rentals.search' or 'rentals.get_pricing' by focusing on the full detail of a single rental.
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?
No explicit guidance is given on when to use this tool versus siblings. The description does not mention scenarios, prerequisites, or conditions that would favor this tool over others like 'rentals.check_availability' or 'rentals.get_pricing'. The agent must infer usage from the tool name and sibling context alone.
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 is clearly scoped to a distinct action within its domain (applications, viewings, rentals, etc.). Verbs like start, update, submit, create, propose, accept are unambiguous and non-overlapping.
All tools follow a consistent domain_verb pattern in snake_case (e.g., applications.start, rentals.search, viewings.propose_availability). No mixing of styles.
21 tools cover a broad rental lifecycle (discovery, applications, quotes, viewings, payments, contracts). While slightly above the typical 15-tool sweet spot, each tool has a defined purpose and no redundancy.
The lifecycle from rental search to booking confirmation and contract signing is well-covered. Minor gaps exist (e.g., no explicit cancellation or withdrawal tools), but the core flows are complete.