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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the description's burden is lower. It still adds real behavioral context: the similarity mechanism, a licensing note on the response, and the exclusion of AI-generated assets, none of which appear in the annotations.

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 sentences, front-loaded with the core action before the return-shape detail. The response-field enumeration is a slight list, but it earns its place because no output schema exists.

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 covers return fields, the licensing note, and the AI-generated exclusion, and the schema covers all parameters. It stops short of saying whether results are ranked by similarity or how ties/empty results are handled, which is a minor gap for a read-only discovery 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 size clamping, category restriction, and image attachment are already fully documented in the schema. The description only echoes the optional category restriction and adds no format or ranking semantics for product_id beyond what the schema says.

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 ('Return products visually and stylistically similar to a given product ID') plus the mechanism ('embedding similarity'). It is inherently distinguishable from siblings like search_products (keyword) and get_product (single-item retrieval) without needing to name them.

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 clearly by the anchor-on-a-product-ID framing, but the description never states when to prefer this over search_products or get_product, nor any prerequisites such as whether the product ID must exist. No exclusions or alternatives are named.

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