b24_products_list

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

No annotations are provided, so the description carries the behavioral disclosure burden. It mentions that products are listed and filterable, but it does not disclose pagination behavior (limit/start/all_pages), default select fields, webhook_url usage, or return shape. This is a minimal disclosure for a tool with no annotation safety hints.

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 front-loaded sentence with the core action and filter scope stated immediately. There is no redundant wording or filler.

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 a 6-parameter tool with a nested filter object, no output schema, and no annotations, one sentence is insufficient. Missing context includes pagination behavior, all_pages semantics, how select works, and whether webhook_url is required for connectivity. The schema covers some parameters, but the tool description does not complete the picture.

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 description points to filter capabilities that map to the 'filter' parameter, but the input schema already documents those examples in detail. It adds no meaningful guidance for the undocumented all_pages and webhook_url parameters, and it does not explain select or pagination semantics beyond what the schema covers.

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 states a specific action ('Lista productos del catálogo') and the resource (product catalog), plus the main filtering dimensions (section, price, active status). It is clear, though it does not explicitly distinguish itself from b24_products_get or b24_read_product_catalog.

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?

No guidance is given about when to use this tool versus b24_products_get, b24_products_sections, or b24_read_product_catalog. The listing intent is implied by the verb, but there are no exclusions, prerequisites, or alternative selection criteria.

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