affiliate_value-commerce-advertiser_list_clicks

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

No annotations provided, so description carries the burden. It discloses return type ('Returns Click records'), the 'recent' temporal scope, and optional filtering by programme/date. It doesn't mention pagination or auth, but for a straightforward read-only list, this is solid 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?

Three sentences, front-loaded with the main function, followed by use cases and a cross-reference. Every sentence adds distinct value with no filler.

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, use cases, and companion tool, but with 7 parameters and no output schema, it misses parameter semantics (especially brand) and doesn't describe Click record fields or pagination behavior. Adequate for a basic list tool 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 coverage is 0%, so description must compensate. It only vaguely references 'programme and date' filters, not their parameter names. It omits the required 'brand' parameter and the pagination params (limit, cursor, offset), leaving significant gaps.

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 states a clear action: 'List recent affiliate clicks on ValueCommerce (advertiser)', with explicit filters ('optionally filtered by programme and date'). It distinguishes from siblings by specifying 'advertiser' and by directing to '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?

Provides explicit use cases: 'traffic-side debugging' with examples like 'are my links being clicked at all?' and 'where is traffic going...'. It also names a complementary tool: 'pair with list_transactions', giving clear guidance on when to use this tool versus alternatives.

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