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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, yet the description adds substantial behavior: the ranking/fallback algorithm, the warning that popularity is not a rating, the fact that purchase flow varies per result and lives in howToBuy, and an explicit untrusted-content warning about seller text. That is meaningful context an agent could not derive from structured fields.

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?

Five short sentences, front-loaded with the purpose and ranking rule, then escalating to result-shape, per-result purchase flow, and a security caveat. No sentence is padding; each carries a distinct fact.

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?

Despite having no output schema, the description compensates by stating that results share genesispay_catalog_search's fields and by pointing to the howToBuy field for per-result purchase flow. Combined with the ranking definition and untrusted-data warning, an agent has everything needed to call and interpret this 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?

Only one parameter (limit) exists and the schema already documents it fully at 100% coverage, including the 1-20 range and default of 10. The description adds nothing about limit, so the baseline 3 for schema-covered parameters 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 (lists) and resource (products trending on GenesisPay) and immediately defines the ranking logic: recent distinct buyers first, newest listing as fallback. It also anchors the result shape to genesispay_catalog_search, letting an agent distinguish it from the sibling search tool without opening a schema.

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 explains what 'trending' means operationally (ranked by recent distinct buyers, newest-listing fallback), which implies when to prefer it over a plain search, but it never states an explicit when-to-use or when-not-to-use rule versus genesispay_catalog_search. Usage is inferable rather than directed.

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