realtime_amazon_data

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 lists operations and parameters but does not disclose behavior such as whether calls are read-only, rate limits, authentication needs, result formats, or edge cases. For a data-access tool, this lack of behavioral context is a notable gap.

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 long but well-structured: a brief overview followed by a compact list of operations with required params, then a clear 'When to use' section. Every sentence serves a purpose, and the format is easy to scan.

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 21 operations and no output schema, the description provides a comprehensive map of operations and their parameters, which is sufficient for selecting and invoking the tool. It does not describe return shapes, but that is less critical for a data retrieval tool and can be inferred from operation names.

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 only defines 'operation' and 'args' generically. The description compensates fully by listing each operation with its required parameters in parentheses, enabling the agent to construct valid 'args' for any operation. This adds essential meaning beyond the schema.

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 Amazon product data with a specific list of operations. It distinguishes itself from siblings by stating 'Use for Amazon specifically' and naming alternative tools for other retailers.

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?

Provides explicit usage guidance: 'Use for Amazon specifically' and directs to alternatives like realtime_product_search for Google Shopping and dedicated tools for Walmart/Costco/Wayfair/eBay. This clearly answers when to use vs alternatives.

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