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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real substance by disclosing the result shape (title, starting price, thumbnail, shop, category, product link), the licensing note in the response, and the important exclusion of AI-generated assets. It omits pagination interplay between size and offset, but the safety and output profile is otherwise well covered.

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 purpose and filters are front-loaded, but the whole definition is one long run-on sentence with a wall of numeric IDs embedded mid-sentence, and the sort/filter enumerations partly duplicate schema enums. The taxonomy earns its place; the structure around it does not.

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 14-parameter browse tool with no output schema, the description covers purpose, filter surface, return fields, and the category taxonomy that the schema abbreviates. Remaining gaps (size/offset interaction, behavior when multiple categories are combined) are minor against full schema coverage.

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 coverage is 100%, so the baseline is 3, but the description earns an extra point by supplying the full category-ID taxonomy (top-level and subcategory mappings for Fonts, Graphics, Templates, Photos, Mockups, Illustrations, Icons) that the schema truncates with 'etc.' That directly reduces the highest-risk failure mode for the required 'categories' parameter.

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?

Opens with a specific verb and resource ('List products in one or more categories or subcategories') and enumerates the filter and sort dimensions, so the agent knows exactly what the tool returns. It does not, however, distinguish itself from the sibling search_products, which appears to overlap heavily with the query-narrowed behavior described here.

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?

Usage is only implied: the description shows that browsing is category-scoped and that 'query' narrows within the category, which hints at when this beats a general search, but it never states when to choose browse_category over search_products or suggest the alternative. No prerequisites or exclusions are given.

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