affiliate_growsurf_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 of behavioral disclosure. It states the return type (TrackingLink) and a precondition (confirm programmeId via list_programmes), but it does not disclose whether the operation mutates state, requires auth, or what error behavior to expect. This is moderate transparency for a link generation tool.

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 concise, containing three sentences that each add value: what it does, when to use, and a return/precondition hint. It is well-structured and free of 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 generation tool, the description covers the core purpose, usage, and return type. However, with no output schema and a required 'brand' parameter left unexplained, plus no detail on error behavior or the TrackingLink structure, it is not fully complete. It is adequate but has clear 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 coverage is 0%, so the description must compensate. It partially covers programmeId (by advising to confirm via list_programmes) and destinationUrl (implied by 'destination URL'), but it does not explain the 'brand' parameter at all, which is required and otherwise undocumented. This leaves a significant semantic gap.

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 GrowSurf for a given programme and destination URL. It uses a specific verb (generate) and resource (tracking link), and the GrowSurf network name distinguishes it from siblings.

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: '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 recommends pairing with list_programmes to confirm the programmeId, which gives a usage hint. However, it does not explicitly state when not to use the tool or mention alternatives for other networks.

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