affiliate_tradedoubler-advertiser_generate_tracking_link

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

With no annotations, the description carries the full burden but doesn't disclose auth requirements, side effects, idempotency, or rate limits. It mentions the return type but other behavioral traits are omitted.

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 concise sentences, purpose first, no filler. Every sentence adds value: purpose, usage context, and prerequisite.

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?

Covers purpose, usage, and return type, but missing parameter details (brand) and behavioral context. For a tool with no annotations and no output schema, it's adequate but has notable 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 covers 0% of parameters. The description explains destinationUrl and implies programmeId via pairing advice, but the required 'brand' parameter is left unexplained, leaving ambiguity.

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 generates a tracking link on Tradedoubler (Advertiser) for a given programme and destination URL. This is specific and distinguishes the tool from other network-specific tracking link generators and the publisher variant.

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 case: 'when the user wants to share an affiliate link to a specific product or page on a merchant they have joined.' Also advises pairing with list_programmes to confirm programmeId. Lacks explicit exclusions but gives clear context.

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