Best and slowest sellers

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds the time-window scoping and the units-sold ranking basis, but it does not disclose additional behavioral traits such as empty-result behavior, pagination, or interpretation of 'bottom' beyond the direction parameter.

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, tightly scoped sentence with no filler. It front-loads the core behavior and avoids restating schema defaults or annotations.

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?

The tool is simple, the output schema is present, and annotations are comprehensive, so the description does not need to explain return values. However, it lacks explicit usage guidance and does not fully describe the limit parameter, leaving minor but real gaps for an agent deciding whether and how to invoke it.

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 0%, so the description must compensate. It effectively explains 'days' (last N days), 'direction' (top or bottom), and the ranking basis, but it does not explicitly explain 'limit' or how it caps the returned product list. The parameter names and defaults make some of this inferable, but a clear statement about limit would be stronger.

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 resource (products) and the metric (units sold) over a configurable time window, and the title 'Best and slowest sellers' reinforces the meaning. It is distinguishable from siblings like get_low_stock or get_sales_summary, though it lacks an explicit verb like 'returns' or 'lists'.

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 is provided about when to choose this tool over alternatives, and none of the sibling tools are mentioned. The description implies its use for top/bottom seller analysis, but there are no explicit conditions, exclusions, or comparisons.

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