affiliate_monetizze_list_clicks

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

No annotations are provided, so the description carries the full disclosure burden. It discloses the return type ('Click records') and optional filters, but leaves unspecified the default date window for 'recent', pagination behavior despite the presence of cursor/offset/limit fields, and any authentication or rate-limit requirements. This is useful but incomplete for a read-only list operation.

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 tightly written sentences front-load the purpose, then add practical use cases and a cross-reference. Every sentence earns its place with no 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?

The tool has 6 undocumented parameters and no output schema, and the description leaves pagination semantics and the meaning of 'recent' unclear. It captures the core purpose and use case well, but is not fully complete for reliable invocation without further clarification.

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 must compensate. It maps 'programme' to programmeId and 'date' to from/to, but does not explain limit, cursor, offset, or the expected date format. The pagination parameters remain ambiguous, which is a significant gap for a 6-parameter tool with no other documentation.

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 verb ('List'), the specific resource ('affiliate clicks on Monetizze'), and the scope ('recent'). It distinguishes the tool from sibling tools by explicitly naming the Monetizze network and contrasting with list_transactions.

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 provides explicit when-to-use guidance with concrete debugging questions ('are my links being clicked at all?') and recommends pairing with list_transactions to compare clicks vs conversions, which effectively communicates the alternative and complementary use case.

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