affiliate_tradetracker_generate_tracking_link

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

With no annotations, the description carries full burden for behavioral disclosure, but only says 'Returns a TrackingLink' without mentioning side effects, auth requirements, rate limits, or whether this creates a persistent resource. The operation's safety profile is unclear for an agent.

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 core purpose, and every sentence earns its place. No filler or redundancy; the use case and pairing hint are valuable additions.

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?

Given the simple two-parameter tool, the description provides core purpose and usage context. However, it omits the authentication prerequisite (common across sibling networks) and gives no detail on the shape or nature of the TrackingLink return value, leaving gaps for an agent to infer safely.

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%, so the description should compensate. It does reference both parameters ('given programme and destination URL') which matches the schema, but adds no format details, constraints, or examples beyond the parameter names themselves.

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 'Generate a tracking link on TradeTracker for a given programme and destination URL' with a specific verb and resource, distinguishing it from sibling tools by network and action. It also specifies the exact inputs, making the purpose unmistakable.

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 to use when 'the user wants to share an affiliate link to a specific product or page on a merchant they have joined' and recommends pairing with list_programmes to confirm the programmeId before calling. This provides clear context and a specific alternative/preparatory step.

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