keepa_search_deals

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'current deals' and 'filtering options' but discloses no return format, pagination behavior, or any other operational traits such as data availability or result ordering, which are not already visible in the schema.

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 a single sentence with minimal waste, front-loading the core purpose. The phrase 'with filtering options' is slightly redundant given the schema but does not significantly detract from the conciseness.

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?

For a tool with 10 parameters, no output schema, and no annotations, the description is too sparse to understand return values, typical use cases, or expected behavior. It lacks the context needed to guide an agent effectively beyond the parameter list, making it insufficient for a tool of this complexity.

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 describes all 10 parameters with clear descriptions (100% coverage), so the description's generic 'filtering options' adds little value. It does not introduce any parameter semantics beyond what the schema already provides, matching the baseline for high schema coverage.

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 action (search) and resource (Amazon deals), with 'current' indicating time-sensitive content. It is distinguishable from siblings like keepa_best_sellers and keepa_price_history by focusing on deals rather than historical data or best-seller lists, though it does not explicitly contrast them.

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 no guidance on when to use this tool versus alternatives. It does not mention scenarios or exclusions, and there is no differentiation from siblings like keepa_product_finder, leaving the agent without criteria for tool selection.

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