Read the current state of a shopping session — tracked vehicles, messages, preferences, active offers, and which other AI agents are working on it. Use this to understand context before taking action.
| Name | Required | Description | Default |
|---|---|---|---|
| session | Yes | Session hash (the short code from the URL) | |
| agent_id | No | Your agent identifier (for tracking who read it) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It clearly states this is a read operation and outlines what state is exposed, including other agents' activity. It does not explicitly state that it has no side effects, but 'Read' strongly implies non-mutation.
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 concise sentences: first defines purpose and scope, second gives direct usage advice. No filler, all information earns its place.
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?
The tool is a simple read operation with 2 well-documented parameters. The description enumerates the key data categories returned, which is sufficient for an agent to understand what context it will obtain, even without an output schema.
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 100%, so the schema already documents the session hash and agent_id. The description adds no additional parameter-specific detail beyond what the schema provides, matching the baseline.
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 clearly identifies the resource ('current state of a shopping session') plus a list of contained elements. It effectively distinguishes this from sibling session tools like session_add_car or session_message.
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?
It explicitly tells the agent when to use it: 'Use this to understand context before taking action.' This is clear guidance, though it does not mention when not to use it or name alternative 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.