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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds that the response carries the total in `total` and cites the underlying endpoint (GET /catalog), which is useful but modest extra context; pagination semantics live in the schema, not the description.

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?

Three short sentences, front-loaded with what the tool returns and what the items are, then filtering provenance. The trailing 'GET /catalog' is mild filler but doesn't obscure anything.

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 covers enough to call correctly: what the collection is, how to filter it, where valid filter values come from, and the presence of `total`. It doesn't describe result shape or pagination flow, though the schema's page/limit text covers the latter.

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 all four parameters are already documented with defaults, ranges, and enum values. The description only adds that category/subcategory values come from the categories sibling, which is helpful provenance but not detail beyond the schema baseline.

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 and resource ('Browse the full CustomCat catalog of printable blank products') and clarifies in parentheses that these are items orderable with your own artwork, which distinguishes it from customcat_get_product and customcat_list_products. An agent can tell what this returns without opening the schema.

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?

Gives clear context for filtering and explicitly routes the agent to customcat_list_catalog_categories for valid category/subcategory values. It doesn't state when to prefer this over customcat_list_products or get_catalog_product, so the alternative-selection guidance is incomplete.

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