zappos_product

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

With no annotations, the description carries the behavioral burden and largely handles it: it states the returned data shape, handles omitted/invalid colorId, and specifies that an unrecognized productId returns 404. It does not mention rate limits or auth, but for a read operation this is a minor gap rather than a misleading one.

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 dense and front-loaded, with each section covering output, parameter source, optionality, and error behavior. There is minor redundancy in the repeated 'full detail' phrasing, but overall no sentence is filler and the structure supports quick agent scanning.

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?

The tool has no output schema and no annotations, so the description is the primary source of behavioral information. It fully accounts for the return fields, the optional parameter behavior, and the failure mode. An agent has what it needs to call this tool 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?

Schema coverage is 100%, so the schema already documents the parameters. The description adds real semantic value by explaining where productId comes from and by clarifying that an omitted or invalid colorId still resolves to a valid base product variant instead of failing.

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 identifies the tool as one that returns a single Zappos product's complete detail, with a specific list of what is included. It is easy to distinguish from zappos_search or zappos_suggest, but it never explicitly names a sibling or states 'use this instead of X.'

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 invocation context: productId should come from a search result's product_id field or a product page URL, and colorId is optional. It stops short of explicitly routing the agent between zappos_search, zappos_brands, and zappos_product, but the provided context is enough for correct selection in most cases.

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