list_dealersAll dealerships with live inventory on CarChat, with city, state, vehicle counts, and each dealer's landing page URL.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| dealers | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds useful context by specifying the filter ('live inventory') and the exact data fields returned, which goes beyond just repeating the annotations. This is meaningful value-added information.
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, tightly written sentence that front-loads the core purpose and lists the returned fields without any fluff. Every word earns its place, making it highly efficient and easy to parse.
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 simplicity (no parameters) and the presence of an output schema, the description is complete. It specifies the scope ('live inventory') and the fields returned (city, state, vehicle counts, landing page URL), so an agent has everything needed to invoke and interpret the tool correctly without further clarification.
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?
There are no parameters, so the schema coverage is 100% and there is nothing for the description to clarify. With zero parameters, the baseline is 4, and the description appropriately offers no redundant parameter details.
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 lists dealerships with live inventory, specifying the included fields (city, state, vehicle counts, landing page URL). The verb 'list' and resource 'dealerships' are unambiguous, and this purpose is distinct from the sibling tools like search_inventory or get_vehicle.
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 does not explicitly state when to use this tool versus alternatives, but the purpose is self-evident from the name and description. The practical use case of retrieving a directory of dealerships is implied, yet no exclusions or alternative conditions are mentioned, so it falls short of explicit guidance.
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 has a clearly distinct role: market stats, individual vehicle details, dealer listings, curated category pages, inventory search, and inquiry submission. There is no meaningful overlap or ambiguity in purpose.
All tool names follow the same verb_noun snake_case pattern: get_, list_, search_, submit_. The naming is predictable and consistent across the entire set.
Six tools is a well-scoped size for a car inventory and inquiry server. Each tool covers a necessary step in the buyer journey without unnecessary duplication.
The tool surface covers the full workflow: searching inventory, retrieving listing details, viewing market pricing, browsing curated categories, finding dealers, and submitting inquiries. There are no obvious gaps or dead ends for the stated purpose.