zappos_brand

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses non-obvious behavior such as real page-based pagination, per-field filter facets, accepted URL/id input forms, and a 404 for unrecognized brands. The main omitted details are the exact response fields, but the core behavioral contract is well covered.

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, front-loaded, and contains no filler. The first sentence states the purpose, the second describes the return content, and the third clarifies input forms and error behavior. Every sentence contributes something the agent needs.

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 that there is no output schema, the description still tells the caller enough to select the tool and understand the result: a product grid with pagination and filter facets, plus the 404 error contract. It could be more complete with exact response fields, but for a browse tool this is sufficient.

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 input schema already documents both parameters at 100% coverage, so the baseline is met. The description adds genuine value by distinguishing accepted brand formats: a full brand URL, the slug/id.zso path, or the opaque id returned by GET /zappos/brands. This materially reduces ambiguity around the main parameter.

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 states a specific operation: browsing a Zappos brand page and retrieving its product grid. It also differentiates the return shape—real page-based pagination and per-field filter facets—which clearly separates this from sibling tools like zappos_brands or zappos_search. The resource and behavior are 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 gives clear context for when to use the tool: when an agent wants a Zappos brand page's product grid. It also tells the caller where the brand identifier can come from, including GET /zappos/brands, which is useful practical guidance. It does not name exclusionary alternatives or explicitly say when not to use it, but the context is strong enough.

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