oldnavy_product_availability

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

With no annotations, the description carries the burden of explaining behavior. It discloses that results are per-size, per-store, with stock statuses of in_stock, out_of_stock, or low_stock, and that the tool resolves nearest stores when zip or lat/lng is given. It could add detail on error behavior or mutual exclusivity of store selection parameters, but the core behavioral content is strong.

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 well-organized: first what it checks, then the pid relationship, then store selection options, then brand values and result content. Every sentence adds operational value, and the most important information (purpose) is front-loaded. There is no fluff.

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?

All essential details are present: required pid, store resolution options, brand mapping, and output statuses. The field is complete enough for an agent to invoke successfully. Minor gaps: no statement about conflict handling if multiple store location modes are provided, and no pagination/rate limit hints, though these are largely irrelevant for a small JSON-response endpoint.

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 description doesn't need to restate parameter semantics. Still, it adds useful meaning by defining brand storefront aliases and clarifying that store_id is pluralizable with comma-separated ids. This exceeds the schema baseline of 3, though the description could go further by explaining conflicting inputs; hence 4 might be slightly generous, 3 is the safe grounded score.

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 states the specific action ('check in-store pickup stock'), the resource ('one color (pid) at one or more physical stores'), and the brand scope (Old Navy, Gap, Banana Republic, Athleta). It distinguishes itself from sibling tools by emphasizing per-size per-store stock status, which is unique among the retail siblings.

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 explicitly explains when to use which store locator input: store_id directly, zip, or lat/lng, and that the latter two resolve nearest stores automatically. It also gives exact brand parameter values (`on`, `gap`, `br`, `at`, default `on`) and clarifies that pid matches oldnavy-product's color-level id, which clearly guides cross-tool usage.

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