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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'recent price drops' and optionally filtered by minimum percent off, but it does not disclose pagination behavior, rate limits, or how the advanced selection override behaves.

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 sentence plus a compact example, with the core purpose front-loaded and no filler. Every element earns its place.

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 read-only listing tool with full schema coverage, the description plus schema is sufficient for an agent to invoke it correctly. The advanced 'selection' parameter is documented in the schema, and the example clarifies typical usage; no output schema exists, but the return shape is reasonably implied by 'deals'.

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 all five parameters are already documented in the input schema. The description's example reinforces domain and min_percent_off usage but adds no new semantic information 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 states a clear resource ('Amazon deals') and a specific action ('recent price drops'), making the tool's purpose obvious. It implicitly distinguishes itself from siblings like keepa_bestsellers and keepa_search, though it does not explicitly name 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 phrase 'Current Amazon deals — recent price drops across the marketplace' provides clear context for when to use the tool: when the agent needs current deal information. It does not explicitly exclude alternatives or route to siblings, but the context is unambiguous enough for basic selection.

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