real_time_wayfair_data

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

With no annotations, the description must disclose behavioral traits, but it only lists operations and required parameters. It does not mention that the tool is read-only, how fresh the data is, pagination, rate limits, or any response format. This leaves the agent uncertain about side effects and return structures.

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 concise and well-structured: a one-sentence purpose upfront, followed by a clear list of operations with required params. Every sentence serves a purpose, and the format makes it easy to parse.

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 three operations and no output schema, so the description should explain what each operation returns. It only names the operations ('Search', 'Product Details', 'Product Reviews') without detailing the response data, pagination, or error behavior. It is sufficient for basic invocation but incomplete for full agent understanding.

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 schema descriptions defer to the tool description for required params, and the description does specify the required parameters for product_details and product_reviews (sku). However, it omits any optional parameters for search and gives no detail on the sku format, leaving the agent to guess. This adds some value but does not fully compensate for the schema's lack of specific param info.

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 tool's scope: 'Wayfair product search, product details and reviews (furniture and home goods).' It identifies the specific resource (Wayfair) and the three operations, distinguishing it from sibling tools like real_time_ebay_data and real_time_walmart_data.

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 provides clear context for when to use the tool: for any Wayfair product data. It does not explicitly list alternatives or exclusions, but the resource-specific name and operations imply its use case. It lacks direct 'when not to use' guidance, but the intended context is unambiguous.

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