affiliate_kwanko_list_clicks

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

With no annotations, the description carries the burden. It discloses that the tool returns Click records and supports filtering, but lacks details on pagination behavior, default date windows, or authentication. It doesn't contradict annotations, but adds only moderate behavioral context.

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 sentences with front-loaded purpose and tight usage guidance. No fluff or redundancy.

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 covers purpose, usage, and return type, but given 6 parameters and no output schema, it leaves pagination semantics and click record fields unexplained. 'Recent' is ambiguous, and no default or range context is provided. It's adequate but with clear gaps.

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 indirectly maps 'programme' to programmeId and 'date' to from/to. It does not explain limit, cursor, or offset, which are key pagination parameters. The description adds minimal semantic value beyond the schema's bare 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 clearly states the tool lists recent affiliate clicks on Kwanko, with optional filtering by programme and date. The verb 'List' and specific resource 'affiliate clicks on Kwanko' distinguish it from transaction-listing siblings like affiliate_kwanko_list_transactions.

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?

Provides explicit use cases ('traffic-side debugging') and concrete example questions, and names a complementary tool (list_transactions) for comparing clicks vs conversions. This gives clear when-to-use guidance and an alternative pairing.

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