keepa_product_finder

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says it finds products with filtering, but gives no information about return format, side effects, authentication, or whether it is a read-only operation. The description adds no behavioral details beyond the purpose statement.

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, front-loaded with the core purpose ('Advanced product finder with filtering'), and contains no unnecessary words. It is concise and well-structured for quick comprehension.

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 19 parameters and no output schema, the description is severely underspecified. It does not explain what the tool returns, how pagination works, how filters interact, or any default behaviors. The schema covers parameter details, but the overall tool context is lacking.

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 has 100% coverage for all 19 parameters with descriptions, so the baseline is 3. The description adds a high-level grouping of filter dimensions (rating, price, sales, competition) that maps to the relevant parameters, but it does not add significant meaning beyond what the schema already provides.

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 finds products with filtering similar to Keepa Product Finder, specifying dimensions like rating, price, sales, and competition level. This distinguishes it from siblings like keepa_product_lookup or keepa_best_sellers.

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 implies usage for product discovery with filtering, but it does not explicitly say when to use this over alternatives like keepa_search_deals or keepa_product_lookup. No exclusions or comparisons to siblings are provided, though the 'similar to Keepa Product Finder' gives some context.

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