list_product_folders

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

With no annotations provided, the description was expected to carry behavioral disclosure. It only states 'List product groups/folders' and adds no detail about pagination behavior, ordering, filtering limitations, permissions, or whether archived/inactive groups are included. The schema's limit/offset parameters imply pagination but the description itself is silent.

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 short sentence, instantly conveying the action and resource. There is no filler or redundant information, making it highly concise and front-loaded.

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?

For a simple list tool, the description might suffice on its surface, but the lack of annotations, output schema, and any context about what constitutes a 'product group/folder' leaves significant gaps. An agent has no way to know what kind of results to expect or when this tool is more appropriate than search_products. The description is incomplete in guiding correct usage.

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 100% (both limit and offset have descriptions), so the baseline is 3. The description adds no additional meaning about parameters, but it doesn't need to given the schema already documents them clearly.

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 has a specific verb ('List') and a resource ('product groups/folders'), making the core purpose clear. However, it does not explicitly distinguish this from sibling tools like search_products or get_product, which could also involve listing/fetching product-related data.

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 provided on when to use this tool versus alternatives (e.g., search_products for filtered queries, get_product for individual items). There is no mention of context, exclusions, or prerequisites.

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