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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context about response content ('base/quote currency, min order size, status, and trading rules') and scope ('all available'), but does not mention pagination, rate limits, or other behavioral nuances. With annotations doing the heavy lifting, this is adequate but not exceptional.

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?

The description is a single, focused sentence that front-loads the core purpose ('list all available trading pairs') and immediately follows with the key fields. Every word contributes value, with no redundancy or fluff.

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?

Given the tool's simplicity (no parameters, clear purpose), the rich annotations (read-only, idempotent, open-world), the existence of an output schema, and the sibling context that clarifies its 'all products' role, the description is complete. It conveys the necessary information for an agent to select and invoke it correctly.

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?

The tool accepts zero parameters (input schema is empty), so the baseline is 4. There are no parameter descriptions needed, and the description does not attempt to invent any, making it appropriate.

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 uses a specific verb 'list' with a clear resource 'all available trading pairs (products)' and enumerates the included fields (base/quote currency, min order size, status, trading rules). It clearly distinguishes itself from sibling tools like 'product' (singular) and product-specific tools by emphasizing 'all'.

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 phrase 'list all available trading pairs' provides clear context that this tool is for the full catalog, implicitly differentiating it from singular product tools. However, it does not explicitly mention alternatives or when not to use it, so it stops short of a 5.

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