affiliate_tolt_list_clicks

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states 'Returns Click records' and implies read-only behavior via 'List', but does not disclose pagination behavior, date range defaults, or whether auth is handled. The description adds context but lacks detail on important behavioral traits.

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 three sentences, front-loaded with the main action, followed by concrete use cases and a pairing suggestion. No redundant information or 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?

Given the tool has 7 parameters, no output schema, and no annotations, the description provides a reasonable overview of purpose and use case, but leaves gaps in parameter semantics and pagination. It is complete enough for tool selection but not fully for reliable 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'filtered by programme and date', mapping to programmeId and from/to, but does not explain required brand, or pagination params (limit, cursor, offset). With 7 params and only partial coverage, the description is insufficient 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 lists recent affiliate clicks on Tolt, with optional filters. It uses a specific verb ('List') and resource ('affiliate clicks on Tolt'), distinguishes it from sibling tools for other networks, and includes concrete debugging examples like 'are my links being clicked at all?'.

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 explicitly says to use for traffic-side debugging and provides example questions. It also recommends pairing with list_transactions to compare clicks vs conversions, which is useful context. However, it does not explicitly say when not to use this tool or mention alternatives other than list_transactions.

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