affiliate_scaleo_generate_tracking_link

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

No annotations are provided, so the description carries the full burden. It adds useful context: 'Returns a TrackingLink' and implies a prerequisite (user must have joined the merchant). However, it does not disclose authentication needs, possible errors, or whether generating a link has any side effects. This is adequate but leaves significant gaps in behavioral detail.

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 concise sentences, with the action stated first, then the usage context, and finally the return type and prerequisite. Every sentence earns its place with no redundancy 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?

For a simple two-parameter tool with no output schema, the description covers the essential context: what it does, when to use it, what it returns, and a prerequisite. It could be more complete with details about URL format or error behavior, but these are not critical for a straightforward link generator. The pairing with list_programmes helps the agent act correctly.

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?

With 0% schema description coverage, the description must compensate. It gives meaning to both parameters: 'programme' and 'destination URL,' and explains the destination is 'a specific product or page on a merchant.' It also advises confirming the programmeId via list_programmes, adding practical semantics beyond the bare schema.

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 states exactly what the tool does: 'Generate a tracking link on Scaleo for a given programme and destination URL.' It uses a specific verb and resource, and the mention of Scaleo distinguishes it from the many sibling generate_tracking_link tools for other networks. It also clarifies the user's intent ('share an affiliate link to a specific product or page').

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?

The description provides a clear trigger condition: 'Use this when the user wants to share an affiliate link to a specific product or page on a merchant they have joined.' It also names an alternative tool to combine with: 'pair with list_programmes to confirm the programmeId before calling,' which is explicit guidance on how to use it correctly.

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