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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the trailing "Read-only" is redundant reinforcement rather than new information. The one genuinely additive line, "Both prices and in/out of stock," hints at the payload contents, but since an output schema exists it adds little behavioral depth beyond ordering or pagination.

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 short sentences with the resource and scope front-loaded and the usage trigger immediately after. The final "Read-only" sentence is pure duplication of the readOnlyHint annotation and is the only wasted wording.

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 two-parameter, zero-required list tool with a full output schema and complete safety annotations, the description covers what the tool returns (ranked best sellers with prices and stock status) and when to call it. Missing only the ordering semantics of the ranking, which is minor.

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 coverage is 100%, with the limit bound (1–20, default 10) and the four-value metal enum documented in the schema itself. The description's "optionally for one metal" only restates the metal parameter at a high level, so this sits at the baseline where the schema carries the load.

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?

The description names a specific resource and scope: best-selling products at Bullion Trading LLC, with an optional single-metal filter. That clearly distinguishes it from siblings like search_products or list_new_arrivals on intent, though neither alternative is named explicitly.

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?

"Use when the user asks which Bullion Trading LLC products sell best" gives a concrete triggering condition rather than leaving usage implied. It stops short of exclusions — it never says to use find_bullion or list_new_arrivals instead when the user wants recommendations rather than a ranking.

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