List categories

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

Annotations already mark this readOnly/idempotent/non-destructive, and the description goes beyond that with real behavioral detail: without a query only levels up to max_level are returned, with a query every level is searched, and the payload includes counts. That conditional scope behavior isn't derivable from the annotations or schema.

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 short paragraphs, front-loaded with what is returned and then how to use it. The parenthetical category enumeration ('clothing, bags, shoes, ...') is mildly expendable but adds domain grounding without bloating the text.

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?

An output schema exists, so the returned-field list is partly redundant, but the description covers the mode selection, parameter interaction, and downstream purpose needed to call it correctly. Nothing operationally important is missing.

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 coverage is 100%, so the baseline is 3, but the description adds the interaction between the two parameters — query triggers a full-depth search while max_level only applies when no query is given. That cross-parameter semantics is not stated in the schema.

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?

States a specific verb+resource ('List Shopino's category tree') and enumerates what is returned: ids, URL paths, levels, plus product and shop counts. That detail plus the category examples clearly separate it from siblings like sh_brands and sh_filters.

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?

Explicitly routes the agent: 'Use to get a category_id for sh_search / sh_browse / sh_find_cheapest', naming three sibling tools and the condition that selects them. It also states the query vs no-query behavior, so the agent knows which mode to pick.

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