Fetch CarMax store location details by numeric ID: name, full address, phone numbers, coordinates, opening hours, and store-type flags.
Get CarMax store (physical location) detail. Returns a CarMax store: name, full address, phone numbers, coordinates, opening hours, and store-type flags (car buying center, microstore).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | CarMax store id, the numeric path segment of a /stores/{id} URL |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It does disclose the return payload (name, address, phones, coordinates, hours, store-type flags), which is genuinely useful since there is no output schema, but it says nothing about read-only safety, error behavior for invalid ids, or id resolution.
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, zero waste, purpose front-loaded ahead of the payload enumeration. Nothing is padded or repetitive.
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 single-parameter lookup with no output schema, listing the returned fields is the key compensation and it is done well. Only the lack of any usage context or id-validity notes keeps it short of fully complete.
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 coverage is 100% and the schema already explains that the id is the numeric path segment of a /stores/{id} URL. The description adds no additional parameter meaning, so the baseline 3 for schema-documented params applies.
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?
States a specific verb ('Get') and resource ('CarMax store (physical location) detail') and enumerates the payload fields. However, it never explicitly distinguishes itself from the sibling carmax_stores (list) or carmax_search tools, leaving the singular-vs-collection routing to inference.
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?
No when-to-use or when-not-to-use guidance is offered, and no alternative siblings (carmax_stores, carmax_search) are named. The agent must infer from the name that this is a single-store detail lookup keyed by id.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.