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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds that it returns a flow in order, the signing messages, and rules, and that the server enforces every rule - useful but modest context beyond the annotations.

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 that leads with the usage condition and then the payload. No filler, no restatement of the name or title.

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 and no parameters, the description has to say what comes back, and it does (ordered flow, signing messages, plain-word rules). It is nearly complete; it could have mentioned that it covers the referral/Squad steps in relation to the individual sibling tools, but nothing critical is missing.

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, so the schema has no semantics to enrich and the baseline is 4. The description correctly implies there is nothing to supply, describing only the returned content.

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 names the domain of the tool (growth flows: recruiting, Squads, referral fees, token reels) and what it produces (ordered flow, signing messages, rules). It is clearly a help/orientation tool and distinguishable in topic from siblings like memeswap_trading_help or memeswap_onboarding_help, though it never explicitly contrasts with them.

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?

"Use first when an agent will recruit people, run a Squad, earn referral fees or post token reels" supplies concrete trigger conditions and an explicit ordering cue ("use first"). It does not name alternative help tools or state exclusions, so it stops short of full when/when-not guidance.

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