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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds meaningful context: the 0.85% fee, the unsigned-construction-only security model, no custody/signing/unrestricted submit, and NFA. This is genuine behavioral disclosure beyond the structured hints.

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 workflow ('First read...quote→unsigned build') is front-loaded and the definition is compact with no wasted sentences. It leans on dense jargon/fragments ('NFA', arrow notation) that slightly reduce parseability but remain efficient.

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 zero-parameter, annotation-covered helper the description orients the agent well, but with no output schema it never says what the agent receives back (guidance text) nor points to the concrete sibling tools to call next (quote/build/chains). Adequate but with clear gaps.

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 per the rubric the baseline is 4; there are no parameters for the description to clarify and schema coverage is vacuously 100%.

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 purpose: a first-read guidance tool for buying meme coins or researching memecoins through a quote→unsigned build flow. It also carves out scope ('Not a token launcher'). However, it does not distinguish itself from close siblings like memeswap_onboarding_help or explicitly tie to memeswap_quote/memeswap_build.

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 clearly signals when to read it ('First read for agents helping users buy a hot meme coin or research memecoins'), which is a strong routing cue. It lacks named alternatives or explicit 'when not to use' beyond the launcher exclusion.

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