Category products

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds a non-obvious behavioral constraint: top-level category paths return no product list, so subcategories are required. It does not discuss pagination, rate limits, or return shape, but the annotations cover the safety profile.

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 two sentences with no filler. The main purpose is front-loaded, followed by prerequisites and the important top-level path caveat.

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 10-parameter read-only listing tool with full schema coverage and no output schema, the description supplies purpose, dependencies, and the critical path constraint. It omits return shape and pagination details, though the schema documents page size and item count.

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%, with detailed per-parameter descriptions for page size, price currency, sort options, spec format, colour format, and boolean filters. The description restates the filter categories and points to ss_filters for spec names, but adds little beyond the already-rich schema. Baseline 3 is appropriate.

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 verb and resource: 'List the products of one Snapp! Shop category or category-brand page,' with the filter scope explicitly named. It also distinguishes its role from ss_categories and ss_filters by referencing them as prerequisite/helper tools.

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?

It gives clear usage context: use after ss_categories, and ss_filters shows spec names. It also provides a concrete exclusion: a top-level path such as 'mobile' has no product list, so the agent must pick a subcategory. It does not explicitly compare against siblings like ss_search for non-category product discovery, but the guidance is strong.

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