list_products

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

No annotations are provided, so the description must convey behavioral traits. It mentions pagination and optional search, but does not disclose rate limits, authentication requirements, side effects (likely none, but not stated), or return behavior when textSearch is empty. The description is minimal beyond the core functionality.

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 a single sentence that is direct and front-loaded with the key action and resource. Every word contributes meaning, with no filler or redundancy.

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 3 parameters, 100% schema coverage, no output schema, and no annotations, the description adequately covers the tool's purpose and key features. However, it lacks details about the return format (e.g., list of product objects with certain fields) and pagination mechanics. The description is mostly 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?

Schema coverage is 100%, so the schema already documents all three parameters (limit, cursor, textSearch). The description adds 'pagination' (covering limit/cursor) and 'optional text search', but these are already implied by the schema descriptions. No additional semantics are provided beyond what is in the schema.

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 action ('List'), the resource ('seller products (cards)'), and key features ('pagination and optional text search'). It effectively distinguishes from sibling tools like get_product (singular retrieval) and others focused on tariffs, campaigns, or orders.

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 via the mention of pagination and text search, but provides no explicit guidance on when to use this tool versus alternatives (e.g., get_product for a single product, or update_prices for modifications). No when-not-to-use or prerequisite hints are given.

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