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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond the annotations – nothing about pagination traversal, default page size behavior, result ordering, or what a smartlink record contains.

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?

It is short, but brevity here comes from under-specification rather than economy – a six-word fragment with no verb and no structure. Nothing is front-loaded because there is effectively no content to front-load.

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 paginated list tool with three parameters and no output schema, the description should at least indicate what is returned and how paging behaves. Instead it supplies only a vague noun phrase, leaving the return contract and the meaning of the rotation qualifier unexplained.

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 100%: page, search and per_page are each documented in the schema, including the max 100 limit and defaults. The description adds no meaning beyond that, so the baseline of 3 applies.

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 is a noun fragment ("Smartlinks with rotation settings.") that never states a verb like list or retrieve, so it only restates the name/title rather than defining the operation. The qualifier "with rotation settings" is ambiguous and could be read as a filter condition, leaving an agent unsure whether this returns all smartlinks or only rotating ones.

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?

There is no guidance on when to use this tool versus the many sibling list operations (list_meta_links, list_campaigns, list_offers, etc.), nor any exclusion or prerequisite. The agent must infer usage entirely from the tool name.

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