carmax_stores

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description discloses the data source ('CarMax's own mobile-app store-locator API'), credential-free access, and the specific fields returned (address, phone numbers, hours, driving distance for ZIP). This is strong transparency for a search tool, though it lacks info on error behavior or rate limits.

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?

Three sentences, front-loaded with purpose, and each sentence adds distinct value (what it does, what it returns, data source). No fluff or 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?

With no output schema, the description covers the key return fields and search behavior, and it clarifies distance applies only to ZIP-based searches. It doesn't describe the exact response structure or edge cases, but for a simple store-finder it's largely 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?

The schema already documents all three parameters with full descriptions, including zip precedence and geo-sort. The description adds no new parameter-level semantics beyond restating ZIP or keyword search, so it only meets 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 opens with 'Search CarMax store (physical location) locations,' using a specific verb and resource, and immediately distinguishes from vehicle-focused siblings like carmax_search by emphasizing physical store locations. It lists concrete output fields, making 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 states searches are by ZIP or free-text keyword, and mentions the ZIP-based geo-distance feature, giving clear context for when to use the tool. However, it does not explicitly name alternative tools (e.g., carmax_search for vehicles) or provide when-not-to-use guidance, so it earns a 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.