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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so safety is covered. The description adds a meaningful behavioral trait — results are ordered by best-selling — but says nothing about pagination, result size relative to 'limit', or the absence of filters.

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 with no filler, and the core resource is front-loaded. Nothing could be removed without losing information.

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 simple read-only browse tool with no output schema and annotations covering safety, this is close to adequate. It still omits what a result looks like (product summaries?), how 'limit' interacts with ranking, and whether the category must be an exact slug match.

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 only 33% schema description coverage, the description partially compensates by explaining where the required 'category' slug comes from. The 'limit' parameter receives no semantic explanation in either the schema or the description, leaving its purpose to be inferred from the min/max bounds.

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 concrete resource and ordering (best-selling products in one category), which tells an agent exactly what comes back. It does not explicitly name how it differs from siblings like search_products or current_deals, so it stops short of full disambiguation.

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 parenthetical '(slug from list_categories)' is an explicit prerequisite that routes the agent to the right sibling for obtaining the required value. There is no stated when-not-to-use or comparison against search_products, but the retrieval path is clear.

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