Signal buyer interest in a vehicle to the dealer. This sends a professional email to the dealership on the buyer's behalf. Only use when the buyer has explicitly indicated interest.
| Name | Required | Description | Default |
|---|---|---|---|
| vin | Yes | VIN of vehicle buyer is interested in | |
| message | No | Optional message to include for the dealer | |
| session | Yes | Session hash | |
| agent_id | No | Your agent identifier |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that the tool sends a professional email on the buyer's behalf, which is a key side effect. However, it does not disclose other potential behaviors such as data persistence, reversibility, or authorization 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 exceptionally concise, consisting of two sentences that front-load the action ('Signal buyer interest') and follow with necessary context. Every word earns its place 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 tool with no output schema, the description adequately covers the primary purpose, the mechanism (email), and a usage condition. It is complete enough for an agent to understand what the tool does and when to invoke it, though it could optionally mention the response or confirmation behavior.
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 input schema provides descriptions for all 4 parameters, achieving 100% schema description coverage. The description does not add additional meaning 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 clearly states the tool's purpose: 'Signal buyer interest in a vehicle to the dealer' with the specific action of sending a professional email. It distinguishes itself from sibling tools like cars_session_message by focusing on interest signaling rather than general messaging.
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 provides explicit usage guidance: 'Only use when the buyer has explicitly indicated interest.' This is a clear condition for when to use the tool, though it does not explicitly name alternatives or contrast with sibling tools.
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.
Most tools target distinct resources (dealer inventory, vehicle search, session actions), but cars_session_message and cars_session_reply have overlapping purposes as both involve posting messages. The session tools are otherwise clearly differentiated by their action verbs.
All tools share the 'cars_' prefix and use snake_case, but the verb-noun pattern is inconsistent: some are action-first (cars_search, cars_session_create) while others are noun-only (cars_vehicle, cars_dealers, cars_history). Session tools follow a consistent 'session_<verb>' structure, but the broader set mixes conventions.
With 19 tools, the set is on the heavy end, falling in the 16-25 range that feels borderline. The count is justified by the comprehensive session workflow, but it approaches the threshold where tool selection becomes cumbersome.
The core journey of searching, inspecting, and tracking vehicles through sessions is well covered, including dealer communication and trade-in. However, there are notable gaps: no way to remove a vehicle from a session or update general buyer profile details (payment method, timeline) after initial creation.