deals

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

No annotations are provided, so the description carries the full burden. The description says deals are fetched but doesn't disclose whether results reflect live availability, whether deals expire/change, pagination behavior, rate limits, or authentication requirements. For a shopping/price tool, freshness and real-time nature of data would be important behavioral context not disclosed.

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 one moderately-sized sentence and is reasonably front-loaded with the core purpose. However, it's somewhat generic and could be tightened. It doesn't enumerate the full filter capabilities despite claiming 'all filters and options' support.

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 12 parameters, no annotations, no output schema, and three parameters having effectively empty descriptions, the tool is under-documented. The description claims broad capability ('all deal types, filters, and options') but this is vague and doesn't enumerate specifics. For a complex tool with this many parameters, more detail on the returned deal structure and how filters interact would be needed.

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 description coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema since it broadly mentions 'filters and options' without detailing specific parameters. Some parameters like lightning_deals, prime_exclusive, and prime_early_access have empty descriptions ('Example value: '), and the main description doesn't clarify their semantics. The description does not compensate for these gaps.

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 'Get Amazon Deals' with specific deal types (Today's Deals / Top Deals, Best Deals, Lightning Deals) and mentions filters/options. It clearly identifies the subject (deals) and distinguishes from sibling tools like deal_products and product_search. However, it could be more specific about what data is returned per deal (e.g., savings, prices).

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?

No guidance on when to use this tool vs. alternatives. With sibling deal_products, best_sellers, and product_search tools, the description doesn't explain what distinguishes deals from best_sellers or deal_products specifically. Context about when one would prefer this over deal_products or best_sellers is absent.

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