list_smart_collections

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

With no annotations, the description must disclose behavioral traits. It only states the purpose (listing) and the nature of collections (automatic/rule-based). It does not mention side effects, authentication requirements, rate limits, or pagination behavior beyond schema parameters. The description adds little beyond the basic function.

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 concise at two sentences, with no redundant information. It efficiently conveys the core purpose. However, it could be slightly expanded with minimal additions to improve completeness without losing conciseness.

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 the tool has 5 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return format, pagination details (beyond schema), common use cases, or how results are ordered. For a listing tool, this context is essential for correct agent 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?

The input schema covers all parameters with descriptions, achieving 100% coverage. The description does not add any additional meaning or context beyond the schema. Thus, the baseline score of 3 is appropriate; no extra value is provided.

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 it lists smart (automatic) collections and explains that products are included based on rules. This distinguishes it from custom collections. However, it does not explicitly differentiate from other list tools like list_collections or get_smart_collection for single retrieval, which would have improved clarity.

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 such as get_smart_collection for a single collection or list_custom_collections for manual collections. The description does not specify prerequisites, limitations, or recommended contexts.

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