affiliate_skimlinks_list_clicks

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions return type ('Click records') and optional filtering, but leaves 'recent' undefined and doesn't discuss auth requirements, pagination behavior, or default time windows.

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 two sentences: the first states the core purpose and filters, the second adds use-case context and a sibling-tool pairing. Every sentence provides value with no 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?

The description is adequate for selecting the tool but incomplete for invocation: it lacks semantics for pagination parameters, leaves 'recent' vague, and there's no output schema to clarify the Click record structure. The use-case examples help, but key execution details are missing.

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 clarifies programme and date filters (programmeId, from, to). The pagination parameters (limit, cursor, offset) are left entirely unexplained, which is a significant gap given the low coverage.

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 explicitly names the action 'List recent affiliate clicks on Skimlinks', identifies the resource, and mentions optional filters (programme and date). This distinguishes it from sibling tools like list_transactions and other network-specific list_clicks tools.

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 provides clear context by stating this is for 'traffic-side debugging' with concrete example questions, and explicitly recommends pairing with list_transactions. However, it doesn't mention when not to use this tool or list alternative tools beyond list_transactions.

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