Read the buyer's trade-in vehicle profile. Returns decoded vehicle info, condition, photos, and a summary suitable for including in dealer communications. Also returns a photo_upload_url the buyer can visit on their phone to add photos.
| Name | Required | Description | Default |
|---|---|---|---|
| session | Yes | Session hash |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does disclose the main returned components and the extra photo_upload_url behavior. However, it does not discuss permissions, error behavior, or whether generating the upload URL has side effects, leaving some behavioral context unclear.
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?
Two sentences efficiently deliver the action, output contents, and the photo-upload URL behavior. The description is front-loaded with the verb and resource, with no unnecessary words.
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?
Since there is no output schema, the description appropriately enumerates the returned items (decoded vehicle info, condition, photos, summary, photo_upload_url) and adds a practical use case. It is complete for a simple one-parameter read tool, though sibling differentiation is left implicit.
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 only required parameter, session, is already fully documented in the schema as 'Session hash', providing 100% coverage. The description adds little beyond the schema, only implicitly connecting the session to the buyer's trade-in context.
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?
Description opens with the specific action 'Read the buyer's trade-in vehicle profile', clearly identifying the resource and distinguishing it from sibling tools like cars_session_tradein or cars_session_read. The returned fields make the tool's function unambiguous.
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 mentions a practical use case ('suitable for including in dealer communications') but does not explicitly state when to use this tool versus alternatives or provide exclusions. Guidance remains implicit rather than direct.
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.