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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds marginal context ('credential-free', 'normalized'), which hints at no auth requirement, but does not disclose pagination, rate limits, or what 'normalized' concretely means for the response.

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 sentence, front-loaded with the verb and resource, with no wasted clauses. The remaining jargon ('normalized', 'credential-free') is mildly opaque but does not bloat the text.

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 a full input schema, an output schema, and annotations carrying the safety profile, the essentials are present. However, for a three-parameter recommendation tool sitting among dense skims_* and other *_product_recommendations siblings, the description offers no routing or usage context to guide correct selection.

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% and all three parameters (handle, limit, intent) are documented in the schema with defaults and allowed values. The description adds no parameter-level detail, so 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?

States a clear verb ('Returns') and a specific resource ('recommended products'), identifying the seed-based recommendation nature that separates it from generic siblings like skims_product or skims_products. It does not, however, name any sibling it is distinguished from, so an agent must still infer routing among the many skims_* tools.

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 description gives no when-to-use guidance, no prerequisite beyond the implicit seed product, and no exclusions or alternatives (e.g., versus skims_product or skims_collection_products). The agent is left to infer the use case entirely.

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