affiliate_partnerstack-advertiser_list_clicks

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

With no annotations, the description must carry the burden. It states it returns Click records and mentions optional filters, but lacks details on pagination (cursor/offset/limit), default date range, and required brand. The read-only nature is implied by 'List', but more behavioral context would improve clarity.

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 efficiently front-load the action and filters, then provide concrete use cases and return type. There is no filler or redundant information.

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 gives a clear high-level purpose and return type, sufficient for selecting the tool, but lacks parameter detail (especially required brand) and pagination behavior. The absence of an output schema makes the minimal 'Click records' return statement less complete, though the pairing suggestion adds valuable context.

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 mentions 'programme and date' filters, leaving brand, limit, cursor, and offset unexplained. The required 'brand' parameter is not mentioned, which is a significant gap for correct invocation.

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 'List recent affiliate clicks on PartnerStack (advertiser), optionally filtered by programme and date', providing a specific verb, resource, and scope. The '(advertiser)' suffix and traffic-side context distinguish it from sibling 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 gives explicit use cases for traffic-side debugging with example questions and suggests pairing with list_transactions to compare clicks vs conversions. However, it does not mention alternatives like the non-advertiser PartnerStack variant, so exclusions are implicit rather than explicit.

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