quotes.getRead one privacy-minimized quote and its live expiry/availability-hold state using the application session that owns it.
| Name | Required | Description | Default |
|---|---|---|---|
| quoteId | Yes | ||
| sessionToken | 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 and idempotentHint=true, so the description adds value by explaining that the quote is 'privacy-minimized' and includes 'live expiry/availability-hold state', which goes beyond the annotations without contradiction.
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 front-loads the action and resource. Every word is necessary and provides value, with no redundancy.
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 simple read tool with an output schema, the description covers the key behavioral aspects (privacy-minimized, live state, session ownership) but does not explicitly state that only the owning session can read the quote. It is mostly complete but slightly ambiguous.
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%, so the description must compensate. It does not explain either parameter (quoteId or sessionToken) beyond the implicit reference to 'application session'. The description adds no specific meaning to the parameters.
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 ('Read') and resource ('one privacy-minimized quote'), and adds unique context about expiry/availability-hold state and session ownership. This clearly distinguishes it from siblings like quotes.create and quotes.accept.
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 the tool should only be used by the owning session ('using the application session that owns it'), but does not explicitly state when to use it versus alternatives like bookings.get_confirmation or viewings.get_status. It provides clear context but no exclusions.
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.