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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It states the tool returns top-rated and in-stock products, implying filtering by rating and availability. This is adequate for a straightforward read operation; no side effects or destructive actions are indicated.

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 only two sentences, with the first clearly stating the purpose and the second providing essential prerequisite guidance. Every sentence adds value, no fluff or repetition.

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 presence of an output schema (so return values need not be explained) and three well-documented parameters, the description is adequate. It covers purpose, prerequisite, and basic behavior. It could mention sorting order (e.g., by rating descending) but is otherwise complete for a simple listing tool.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds the context of 'top-rated' and 'in-stock' but does not explain parameter syntax or usage beyond what the schema already provides (e.g., defaults and ranges).

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 lists top-rated in-stock products within a specific iHerb category, providing a specific verb (list), resource (products), and scope (category). This distinguishes it from sibling tools like get_supplement_detail (single product) and list_categories (lists categories).

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 explicitly instructs to use list_categories first to discover valid category slugs, which is excellent guidance for the agent. It implies when to use this tool (when you have a category and want top-rated in-stock items) but does not explicitly state when not to use or mention alternatives like search_supplements.

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