affiliate_flexoffers_generate_tracking_link

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

No annotations are present, so the description must disclose behaviors. It states the output ('Returns a TrackingLink') and suggests verifying the programmeId first, but does not mention auth requirements, error conditions, or whether the operation is non-destructive. Adequate but with gaps.

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, front-loaded with the action and resource. Every sentence adds value: purpose, use case, return type, and a pairing instruction. No redundancy.

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?

For a simple 2-parameter tool with no output schema and no annotations, the description covers purpose, trigger, return type, and prerequisite. It does not explain failure modes or exact formats, but the essential context is present.

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 has zero field descriptions, so the description compensates by naming the two inputs ('programme and destination URL') and explaining programmeId's source via list_programmes. Does not specify URL format, but enough for an agent to invoke correctly.

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?

States 'Generate a tracking link on FlexOffers for a given programme and destination URL'—a specific verb, resource, and parameters. The network name and action distinguish it from sibling generate_tracking_link tools across other networks.

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?

Explicitly says 'Use this when the user wants to share an affiliate link to a specific product or page on a merchant they have joined' and instructs to 'pair with list_programmes to confirm the programmeId before calling.' Lacks explicit when-not-to-use alternatives, but the companion instruction is useful.

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