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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the exact result fields returned, that the response carries a licensing note, and that AI-generated assets are excluded from results — non-obvious filtering behavior an agent could not infer elsewhere.

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?

Content is front-loaded — resource and scope first, then filters, sort, returns, and exclusions. It is compressed into essentially two very long sentences, which is dense but every clause carries information; the filter enumeration in particular could have been deferred to the schema instead of restated.

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 usefully documents the result shape (title, starting price, thumbnail, category, product link), the licensing note, and the AI-generated exclusion. For a 12-parameter read tool with no output schema, this covers most of what an agent needs, though pagination behavior beyond the offset parameter is not described.

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%, including the AND-vs-OR semantics of width/weight versus properties and the size floor of 9, so the schema does the heavy lifting. The description only paraphrases the filter names at a high level and adds no syntax or interaction detail beyond what the schema already documents.

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 designer or studio by numeric shop ID') and enumerates the narrowing filters and sort modes, so an agent knows exactly what this does. It implicitly distinguishes itself from search_products via the single-shop scope, but never names that sibling to make the boundary explicit.

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?

Usage is implied by 'one designer or studio by numeric shop ID' — an agent can infer this is the per-shop browse path versus a global search. However, there is no explicit when-to-use/when-not guidance, no mention of browse_category or search_products as alternatives, and no stated prerequisite that a shop ID must first be obtained.

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