smartscout_top_products

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

With no annotations, the description carries the full burden, and it discloses almost nothing behavioral: no indication of how 'top selling' is ranked (units vs. revenue), no pagination or limit behavior, no auth or rate-limit notes, and no return-shape hint. Only 'Get' weakly implies a read operation.

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 short sentence that front-loads the verb and resource with no filler. It is efficient, though the brevity contributes to the coverage gaps noted elsewhere rather than to clarity.

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 4-parameter tool with zero annotations and no output schema, the description is too thin: it never defines the ranking basis for 'top selling', the role of the limit default, or how brand interacts with category/subcategory. An agent can call it, but cannot predict what it returns.

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 four parameters are already documented, making 3 the baseline. The description mentions category/subcategory filtering but adds no syntax or relationship detail (e.g., whether both can be combined) and omits the brand filter entirely.

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?

States a specific verb and resource ('Get top selling products') and constrains scope to a category or subcategory. However, it does nothing to distinguish itself from the very similar sibling smartscout_top_sellers or from smartscout_product_search, leaving the agent to guess which retrieval tool fits.

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?

There is no guidance on when to pick this over smartscout_top_sellers, smartscout_product_search, or smartscout_custom_query, nor any prerequisite or exclusion noted. Usage is only implied by the word 'top'.

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