affiliate_mrge_list_clicks

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

No annotations provided, so description carries full burden. It does not disclose pagination behavior, default date range for 'recent', authentication requirements, or rate limits. 'Returns Click records' is functional but not behavioral; lacks detail about cursor/offset/limit semantics.

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, front-loaded with the action. Each sentence adds value: purpose, usage examples, and cross-reference to list_transactions. No wasted words.

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 6-parameter tool with no output schema and no annotations, the description leaves critical gaps: pagination params unexplained, no return structure beyond 'Click records', no mention of sorting or default ranges. Incomplete for correct invocation.

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?

With 0% schema coverage, description must explain all parameters. It mentions 'programme' and 'date' (matching programmeId and to/from) but says nothing about limit, cursor, or offset. Date format and optionality are unspecified.

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?

Description clearly states 'List recent affiliate clicks on mrge, optionally filtered by programme and date' — specific verb, resource, and scope. It distinguishes from siblings by focusing on clicks and explicitly pairing with list_transactions for conversion comparison.

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?

Explicitly says 'Use this for traffic-side debugging' with concrete example questions, and names the complementary tool list_transactions for click-vs-conversion analysis. This gives clear when-to-use guidance and an alternative.

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