Catalog structure

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds that categories carry their parent so the tree can be rebuilt, but says nothing about pagination, result size, or what happens when a section is empty.

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?

One tightly packed sentence that leads with the returned resources and uses the parenthetical only to justify why parent data matters. No filler, though the four-resource list plus aside is slightly dense.

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?

With no output schema, the description does much of the work by naming the returned entity types and their IDs, which is good. However, it omits the existence of the text filter and any indication of result shape or volume, leaving gaps for a catalog-listing tool.

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%, so the single 'q' parameter (full-text filter applied to every section) is already fully documented. The description adds no extra meaning about filtering behavior, so the baseline 3 applies.

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 enumerates the concrete resources returned (product categories, collections, tags, product types), which clearly separates it from siblings like list_products or list_customers. The retrieval verb itself is only implied by the tool name, but the resource scope is unambiguous.

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 phrase 'with IDs for other tools' implies the intended workflow (fetch IDs to feed save_category, delete_category, save_collection, etc.), but there is no explicit when-to-use or when-not-to-use statement, nor any mention of an alternative tool.

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