List ClickBank products

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds site scoping and filter behavior, but it does not mention pagination, result limits, or whether the list can be considered exhaustive, so operational behavior remains partially unspecified.

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?

Two short sentences with no filler. The primary scope is stated first, and the optional filter is stated second; every part of the description earns its place.

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 low-complexity, read-only list operation with one required and one optional parameter, the description provides the necessary invocation context. A small gap is the lack of any note about return shape or pagination, especially since no output schema is provided.

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 50%: 'site' is already described, while 'type' has no description. The description compensates by framing 'type' as an optional STANDARD/RECURRING filter, giving the agent useful meaning beyond the raw enum names.

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 and resource: 'List products' for a 'site nickname', and adds the optional STANDARD/RECURRING filter. This is enough for an agent to distinguish it from siblings like get_product or list_orders without needing to inspect schemas.

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 implies when to use the tool: when you want products owned by a site, optionally narrowed by product type. However, it names no alternatives and gives no explicit 'when not to use' guidance, leaving the choice among sibling tools to inference.

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