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

Annotations already carry readOnly, idempotent, and non-destructive traits; the description adds pagination behavior with offset and the returned field list. It does not mention errors or rate limits, but the annotation coverage lowers the burden.

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?

Three short sentences with zero filler; the core purpose, returned content, and pagination guidance are all front-loaded. Every sentence earns its place.

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?

Output schema supplies return structure and annotations cover safety, while pagination guidance appears in both the description and schema. The only gap is explicit alternative selection, which is not required for a straightforward catalog-list 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?

Schema covers both parameters at 100%, including defaults and next_offset semantics. The description adds the phrase 'page with offset' but does not provide additional meaning beyond what the schema already documents.

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?

States a specific verb ('List') and resource ('products in this store') and enumerates the returned fields (title, price, sale price, availability, image, URL). The catalog/browse framing separates it from more targeted tools like get_product or search_products, though it does not name them explicitly.

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?

Provides clear context: it returns the catalog for browsing and instructs to page with offset, explicitly routing cart-building to add_to_cart. It does not state when to prefer this over search_products or best_sellers, but the catalog-browsing purpose is enough for an agent.

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