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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered. The description adds useful context beyond that: the endpoint is 'credential-free' (no auth needed) and results are 'normalized', but it says nothing about rate limits, pagination, or what happens with an invalid handle.

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 tight sentence with the core action front-loaded and zero filler. It could be slightly better by spending a clause on when to use it instead of the implementation detail 'Ajax endpoint', but it is efficient.

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?

An output schema exists, so return values need not be explained, and annotations carry the read-only/open-world profile. The gap is the absence of routing guidance among the large family of sibling recommendation tools, but for a simple one-required-param read tool the description is largely sufficient.

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, including defaults and allowed values. The description adds no parameter meaning beyond that, 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 specific verb and resource ('Returns normalized recommended products') plus the data source ('Rebag's recommendations Ajax endpoint'), so the agent knows exactly what it fetches. It does not, however, distinguish itself from the many sibling *_product_recommendations tools or from related Rebag tools like rebag_product or rebag_search, so sibling differentiation is left to the name prefix.

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 guidance on when to choose this tool over rebag_product, rebag_search, or rebag_products, nor any prerequisite or exclusion. 'Credential-free' hints at accessibility but is not framed as a usage condition.

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