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

Annotations already declare this a read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description adds real substance beyond that: it discloses the returned content (referral link, App Store link, reels with AI disclosure requirements, copy rules) and that output is prose rather than structured data. It does not explain size, caching, or freshness of the guidance.

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?

A single front-loaded sentence led by the usage trigger, with no filler or restatement of the title. The parenthetical list of returned artifacts is dense but each item earns its place by telling the agent what to expect back.

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 does the work of previewing the return value (attribution links, disclosure rules, copy rules), which is exactly what a zero-parameter help tool needs. No prerequisites, auth requirements, or scope limits are stated, but for a read-only informational endpoint the remaining gap is small.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to clarify. The parenthetical enumerating outputs is more relevant to return content than to parameters, so no credit or penalty is warranted here.

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 specific action and resource: it returns promotion instructions with attribution (referral link, App Store link, reels with AI disclosure) plus copy rules. It is clearly a guidance/help tool, but it never distinguishes itself from near-neighbors like memeswap_growth_help, memeswap_onboarding_help, or memeswap_brand_kit, so an agent must infer the boundary.

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?

The opening clause 'Use when an agent will promote MemeSwap anywhere' gives an explicit trigger condition, which is more than most help tools offer. It stops short of saying when to prefer this over the sibling *_help tools or brand_kit, so the alternative-selection guidance is implied rather than stated.

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