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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond purpose — no pagination behavior, ordering, result caps, or filtering semantics — leaving the behavioral picture thin for a listing endpoint.

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?

A single front-loaded sentence with no filler. Despite being short, every word contributes to identifying the resource and its scope.

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?

For a 3-parameter, 2-required listing tool with no output schema and no parameter documentation, the description is too sparse. An agent gets no sense of the result shape, default ordering, or how query/siteId/projectId constrain the listing.

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 0% for three parameters (query, siteId, projectId), and the description never mentions them. It only hints that products are scoped to something articles can feature, which weakly implies site/project context but does not explain the required IDs or what 'query' matches. It fails to compensate for the coverage gap.

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 (list) and resource (products) and adds a clarifying scope — products that articles can feature — which distinguishes it from the mutating siblings create_product, update_product, delete_product, and set_product_status. It does not differentiate itself from other read/list tools in the catalog, but the core purpose 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?

There is no explicit when-to-use guidance, no mention of alternatives, and no prerequisite context. An agent must infer from the name alone that this is the read counterpart to create_product/update_product rather than, say, list_linkable_assets.

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