rr_get_top_sellers

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

No annotations are provided, so the description must disclose behavioral traits. 'Get' implies a read-only operation, but no details are given about what 'top-selling' means, whether data is aggregated, or if there are limits or side effects. The description adds minimal transparency beyond the implicit read hint.

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?

At only 6 words, the description is extremely concise but at the expense of completeness. It fails to include essential information that would make the tool usable without consulting other documentation.

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?

Given 3 parameters, no output schema, and many sibling tools, this description is severely incomplete. It does not explain the output format, how results are ranked, or how to handle empty results. The agent lacks enough context to use this tool effectively.

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%. The description does not explain any parameter meanings, such as that 'days' controls the lookback period, 'limit' caps the number of results, or 'store_id' filters by store. The agent must infer from names alone, which is insufficient.

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 'Get top-selling SKUs' clearly identifies the verb 'Get' and the resource 'top-selling SKUs'. It is specific enough to convey the basic purpose, but it does not differentiate from sibling tools like rr_get_sales_history or rr_get_slow_movers.

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 usage guidance provided. The description does not explain when to use this tool versus alternative analytics tools (e.g., for broader sales data, use rr_get_sales_history; for slow movers, use rr_get_slow_movers).

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