List products

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

With no annotations provided, the description carries the full behavioral burden and discloses nothing: no pagination semantics despite page/size parameters, no auth or rate-limit context, no statement of what is returned, and no read-only confirmation beyond what the verb GET incidentally implies.

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?

It is short, but this is under-specification rather than conciseness; a single fragment with no front-loaded purpose statement or useful structure. Nothing wastes words, but nothing earns them either.

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 three undocumented parameters, no annotations, no output schema, and a dense sibling set of product/customer tools, the definition is far too thin for an agent to invoke it correctly or choose it over alternatives.

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 description coverage is 0% and the description adds no parameter meaning whatsoever. Three parameters (page, size, language_code) with defaults, bounds, and a pattern are left entirely unexplained, including what language_code actually filters.

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 is a bare HTTP route string, 'GET /product/list.', which merely restates the tool name and title rather than describing the operation in agent-facing terms. It conveys no scope, filtering behavior, or distinction from the many product-related siblings such as get_product or list_customer_products.

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?

There is no when-to-use guidance at all: nothing says when to call this instead of get_product, list_customer_products, or search_customers. The route string implies a generic listing but offers no conditions, prerequisites, or exclusions.

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