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

Annotations only carry title and destructiveHint, so the description adds genuinely useful context: the plan gate and the token auto-generation default. It still omits the mutation's side effects, idempotency, and what the call returns, which is notable given the odd destructiveHint=true on a create operation.

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?

Three short sentences with the core action front-loaded and no filler. The trailing "Rewardful: POST /v1/affiliate_links" is implementation detail that is marginally useful for an API-aware agent but is the weakest part of an otherwise tight description.

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?

With no output schema, the description should say what a successful creation yields (the created link/token), which it does not. Plan gating and the token default are covered, so it is adequate but incomplete for a creation tool.

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 100%, so the baseline is 3, and the description adds meaning beyond the schema by clarifying that the token parameter is optional and auto-produced when omitted. It does not, however, explain the affiliate_id semantics beyond what the schema already documents.

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 a concrete action (create an additional tracking link) on a specific resource tied to an affiliate, which separates it from siblings like create_affiliate_coupon or create_campaign. It is clear without opening the schema, though it never explicitly names the create verb or names a sibling to disambiguate against.

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?

"Growth/Enterprise plans only" gives a real precondition, and "A token is generated if omitted" implies when the token param is optional. However, there is no explicit when-to-use vs alternatives guidance (e.g., when to add a second link vs rely on the default link), leaving selection implicit.

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