get_top_selling_products

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

With no annotations provided, the description carries full burden. It states it returns top selling items but does not disclose how 'top selling' is defined (e.g., by quantity or revenue), whether it aggregates data, or any other behavioral traits. This lack of detail reduces transparency.

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 sentence followed by a purpose statement, both concise and front-loaded with the key action. No filler or redundant phrases.

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 three parameters, no output schema, and no annotations, the description is minimal. It lacks details on response structure, pagination, sorting, and the exact definition of 'top selling.' The agent may not have enough to use the tool confidently without further inference.

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?

All three parameters (branch, period, per_page) are fully described in the input schema with defaults and constraints. The description adds no additional semantic information beyond what the schema already provides. With 100% schema coverage, the baseline is 3.

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 states the tool retrieves top selling food menu items by time period and branch, with a stated purpose of menu optimization and promotions. It distinguishes itself from sibling tools like list_products and get_product, though it does not explicitly contrast with 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 description mentions it is 'useful for menu optimization and promotions,' providing some guidance on when to use it. However, it does not specify when not to use it or explicitly compare to alternative tools such as get_product for individual product details.

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