oldnavy_product

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

No annotations are provided, so the description carries the full burden. It discloses that the return is normalized to one color variant, everything offers beyond sizes are separate priced offers, and the pid must be color-specific rather than a base product id. It omits error behaviors or auth/rate-limit notes, but the essential behavioral quirk is filled.

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?

Each of the three sentences carries a distinct purpose: brand scope, return payload, and pid/brand parameter guidance. The description is a bit dense with dashes a semicolon, but no sentence is filler.

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 only two parameters, no output schema, and no annotations, the description gives enough to select and invoke the tool correctly, including return content and parameter semantics. It would be fully complete if it briefly covered error/return-shape edge cases, but that is not essential.

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?

Despite 100% schema coverage, the description adds concrete value: for brand it enumerates the valid values (`on`, `gap`, `br`, `at`) and documents the default, and for pid it states the exact source field and explicitly warns 'not the bare base product id' and the requirement that pid matches the brand. This goes well beyond the schema's terse property descriptions.

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 a concrete verb and resource ('Get an Old Navy, Gap, Banana Republic, or Athleta product') and immediately defines the exact scope: one color variant, with a specific return payload (name, description, images, aggregate rating, size-priced offers). It also distinguishes itself from sibling product tools by explaining that pid is a color-specific product id, not the bare base product id.

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?

It gives clear usage context: this tool is intended after obtaining a pid from oldnavy-search's product colors[].id field, and the brand must match the storefront under which the pid was found. It doesn't explicitly list alternatives like oldnavy_product_reviews or oldnavy_product_availability, but the intended workflow is well communicated.

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