affiliate_lomadee_generate_tracking_link

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

With no annotations provided, the description carries the full burden. It does add 'Returns a TrackingLink' and a prerequisite to confirm programmeId, which is useful. However, it does not disclose authentication requirements, error behavior, or other side effects, leaving some transparency 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?

The description is three sentences, all information-dense and front-loaded with the action. Every sentence adds value: purpose, usage context, return type, and a prerequisite. No fluff or repetition.

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 or annotations, the description covers the core purpose, usage context, return value, and a required prerequisite. It lacks additional context like authentication or error handling, but these may be less critical given the tool's simplicity.

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 must compensate for the schema's bare strings. It only refers to 'given programme and destination URL' without adding details about ID format, URL constraints, or examples. This falls short of what an agent needs to correctly populate the parameters.

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 it generates a tracking link on Lomadee for a programme and destination URL. This distinguishes it from other network-specific generate_tracking_link tools in the sibling list, and the verb 'generate' plus resource 'tracking link' is specific.

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 advises pairing with list_programmes to confirm the programmeId. However, it does not explicitly mention when not to use it or name alternative tools.

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