affiliate_digistore24_list_clicks

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

No annotations are provided, so the description must carry the transparency burden. It adds 'Returns Click records', which clarifies the output type, and the 'List' verb implies read-only behavior. However, it leaves 'recent' undefined and does not mention pagination, default date range, or cursor/offset behavior, leaving meaningful gaps.

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 sentences are front-loaded: purpose, use case, then return value/companion tool. No wasted words; the examples add concrete value.

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 good purpose framing, there is no output schema or annotations, and the description fails to explain pagination parameters, date range semantics, or what a Click record contains. For a 6-parameter tool with no parameter descriptions, this leaves the agent to guess at critical invocation details.

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 0%, and the description only says 'optionally filtered by programme and date', which loosely maps to programmeId and from/to but not to limit, cursor, offset, or their formats. With six unannotated parameters, this is insufficient compensation.

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 opens with 'List recent affiliate clicks on Digistore24, optionally filtered by programme and date', naming the exact resource and verb. It distinguishes this from Digistore24's list_transactions and from other networks' list_clicks by naming Digistore24 and focusing on clicks.

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?

It explicitly says 'Use this for traffic-side debugging' and gives concrete example questions, which tells when to invoke it. It also points to list_transactions as the conversion-side complement, though it does not mention explicit 'do not use for conversions' exclusions or other alternative tools.

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