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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does add real behavioral context: result ordering, default page size, and ANDed filter semantics. It stops short of covering total counts, max page behavior, or what an empty result looks like.

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 compact sentences with zero filler; ordering and page-size defaults are front-loaded before the return-field enumeration and the ANDed-filter rule. Every clause carries information.

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 read-only list tool with no output schema, the description covers ordering, pagination default, filter combination logic, and the general shape of returned data. Only total-count/pagination-boundary behavior is left unstated, which is a minor gap.

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 88%, so the schema already documents page, user_id, product_id, affiliate_id, created_after/before and items_per_page. The description's 'product, price, discount, tax, coupon...' list actually describes returned fields, not inputs, so it adds no parameter meaning beyond the schema.

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 ('List payments') and adds useful scope detail: ordering (newest first), default page size (50), and the returned field set. It implicitly separates itself from the sibling learnworlds_get_payment (single-payment lookup) but never names it 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?

Usage is implied by the list-vs-get naming rather than spelled out; there is no explicit 'use this instead of X when Y'. The note that 'All filters are ANDed' is genuinely useful invocation guidance, which nudges it above a bare 2.

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