run_wayfair_products

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a genuine non-obvious trait — the flat 5-point cost per successful run — and the exact field set returned, but it says nothing about failure behavior for an invalid SKU/URL, whether the call is read-only, or any rate limits.

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?

Two sentences, front-loaded with the verb and lookup key, followed by the returned fields and the cost. The field enumeration is long but each item is informative rather than filler; no preamble or redundancy.

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?

There is no output schema, so enumerating the return fields (title, brand, price, list price, discount, rating breakdown, images, variants, verified status, availability, category) is exactly the right compensation, and the cost note is a useful extra. Only the missing error/edge-case behavior keeps it short of complete.

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?

With one parameter and 100% schema description coverage (the schema already says 'SKU or product URL. e.g. W114765796'), the schema does the heavy lifting. The description restates the accepted input forms but adds no format or validation detail beyond it, so the baseline of 3 applies.

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 verb and resource ('Get full Wayfair product details') and pins the lookup key ('by SKU (or product URL)'), then enumerates the returned fields. It is clearly distinguishable from a search-style tool, but it never names its obvious sibling run_wayfair_products_search, so differentiation is left to inference.

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?

Usage is implied rather than stated: an agent can infer this is the detail lookup for a known SKU, versus the search endpoint. There is no explicit when-to-use/when-not-to-use guidance and no alternative named, so it is only minimally viable.

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