Retrieve Best Buy's complete brand directory with names, category IDs, and URLs. Use each ID directly as the category_id input for Best Buy category queries.
Get Best Buy's full brand directory. Returns Best Buy's full brand directory (name, category id, url), sourced from the site's own "Name Brands" page. Each id is directly usable as bestbuy_category's category_id input.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It explains the data is sourced from Best Buy's own 'Name Brands' page, identifies the returned fields, and even documents the downstream compatibility of IDs. It doesn't mention pagination or response formatting, but for a simple full-directory retrieval this is reasonably transparent.
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 short and front-loaded with the main purpose. It does contain minor redundancy—"Get Best Buy's full brand directory" and "Returns Best Buy's full brand directory" overlap—but the remaining details about the source and downstream ID usage earn their 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?
For a zero-parameter directory-listing tool with no output schema, the description supplies the essential context: what is returned, the field names, the source of truth, and how to use the IDs in a related tool. Nothing material is missing for an agent to invoke it correctly.
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 tool has zero parameters, which means there are no input ambiguities for an agent to resolve. The schema description coverage is complete by virtue of having no properties, so the description does not need to add parameter-level 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 uses a specific verb and resource: "Get Best Buy's full brand directory." It also states the returned data shape (name, category id, url), which makes what the tool does immediately clear and distinguishes it from sibling tools like bestbuy_categories or bestbuy_product.
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 gives clear context: use this tool when you need Best Buy's full brand directory, and it explicitly explains how the returned IDs feed into bestbuy_category. It doesn't list excluded cases or alternative tools explicitly, but for a zero-parameter reference-list tool that context is sufficiently actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.