smartscout_top_sellers

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

With no annotations, the description carries full behavioral burden but discloses almost nothing beyond the basic action. It does not mention authentication needs, rate limits, pagination, result ordering, or whether 'top' means top-N by default, so the agent has little behavioral context beyond the schema defaults.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its extreme brevity leaves limited room for structure.

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 (3 optional params, all documented, no output schema, no annotations). For such a low-complexity tool, one sentence is minimally adequate, but the absence of any usage or behavioral context for a tool with no annotations means it falls short of being fully complete.

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 the schema already documents limit, metric, and minRevenue, making the baseline 3 correct. The phrase 'by revenue or other metrics' loosely echoes the metric parameter but adds no syntax or format detail 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 specific verb and resource ('Get top sellers') plus the ranking dimension ('by revenue or other metrics'), so the agent knows what the tool returns. It does not differentiate from the sibling smartscout_top_products, which ranks products rather than sellers, leaving that distinction to be inferred.

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 only usage hint is that ranking can use 'revenue or other metrics,' which merely mirrors the metric enum. There is no guidance on when to prefer this tool over smartscout_top_products or other seller-related siblings, and no prerequisites or exclusions are given.

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