dw_product_list

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

With no annotations, the description must disclose behavioral traits. It mentions pagination (pagingSize) and returned fields, but does not cover authentication, rate limits, or whether the operation is read-only (assumed). The absence of destructive hint is acceptable for a list, but more detail on pagination limits would improve transparency.

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?

Two concise sentences covering purpose, filters, outputs, and pagination. No redundant information. Could be slightly better structured, but efficient for an agent to parse.

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 5 parameters and no output schema, the description partially covers outputs and filtering but omits details on languageId, pagingIndex, error handling, and rate limits. It is adequate for a simple list tool but not fully comprehensive.

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 low (40%). The description adds minimal value: it restates groupId and search (already in schema) and provides a vague hint for pagingSize ('control result count'). It ignores languageId (default only) and pagingIndex, leaving their meaning unclear. For a tool with 5 parameters, this is insufficient.

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 tool lists DynamicWeb products, specifies filtering by groupId or search term, and lists returned fields. It distinguishes from sibling tools like dw_product_get (single product) and dw_product_category_list (categories).

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 when to use (listing products with filters) but does not explicitly state when not to use or compare to alternatives. It lacks guidance on using dw_product_get for individual products or dw_product_update for modifications.

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