affiliate_flexoffers_list_clicks

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

With no annotations provided, the description carries the full burden. It adds 'recent' and 'Returns Click records' but does not disclose pagination behavior, default time windows, date formats, or authentication requirements. This is partial but not comprehensive behavioral disclosure.

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 two sentences, front-loaded with purpose. Every clause earns its place: purpose, usage context, return type, and pairing advice. No unnecessary wording.

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 is acceptable for a simple list tool but lacks specifics on pagination parameters, default date range, and return field details. Given no output schema and 0% param descriptions, more detail would be needed for fully informed usage. It is 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 coverage is 0%, so the description must compensate. It clarifies that filters by 'programme and date' (mapping to programmeId and from/to), but leaves limit, cursor, and offset unexplained. It adds some meaning but does not fully cover all six parameters.

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 'List recent affiliate clicks on FlexOffers, optionally filtered by programme and date' with a specific verb and resource. It distinguishes from siblings by naming FlexOffers and mentioning pairing with list_transactions, making its scope explicit.

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 concrete when-to-use context ('traffic-side debugging') and examples ('are my links being clicked at all?'). It names list_transactions as a complementary tool but does not explicitly state when not to use this tool.

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