get_overall_top_products

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a list of dictionaries or an error message, but does not explain how 'top' is determined beyond sort parameters, nor does it mention side effects, rate limits, or error details. Adequate but limited.

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 concise, front-loaded with purpose, and structured with Args and Returns sections. Every sentence adds value, no wasted words.

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 the absence of annotations and output schema, the description covers parameters, return format, and purpose fairly completely. It lacks details on error cases and the exact meaning of 'top' but is adequate for the context.

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?

With 0% schema description coverage, the description adds substantial meaning: clarifies k must be positive integer, sort_by examples (score, price), sort_order options (asc/desc), fields as optional list. This goes beyond the schema's type/defaults, though not exhaustive on valid sort_by values.

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 K products across all stores, using a specific verb and resource. It distinguishes itself from sibling tools like get_product_details_by_url or query_store_products which are not about overall top products.

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 implies usage when needing top products across all stores but does not explicitly state when to use this over alternatives. No exclusions or comparisons with sibling tools are provided, leaving the agent to infer.

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