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. The description adds useful scope guarantees beyond that ('No custody / no auto-trade') and notes that the human signs, which is genuine added context. It stops short of saying what the tool actually returns or that the 'connect wallet / set avatar' steps are instructions rather than side effects, leaving mild ambiguity against the readOnlyHint.

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 core purpose is front-loaded in the opening clause and the whole description is one compact sentence with no filler. The fragment 'wallet-ref duct' is garbled and slightly impairs comprehension, but the structure is otherwise 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?

With no parameters and no output schema, the description carries the burden of explaining what an agent gets back, and it does not: it never says this returns onboarding guidance/steps. Annotations cover the safety traits, so the remaining gap is the return expectation and the relationship to the sibling action tools.

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 and the schema is empty with additionalProperties=false, so there is no parameter meaning for the description to supply. The baseline for a parameterless tool 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 names a concrete domain (onboarding a human signer for non-custodial meme buys via MCP) and enumerates the covered steps, so the general subject is graspable. However, it never makes clear that this is a help/orientation resource rather than an executor, even though sibling tools (memeswap_set_avatar, memeswap_set_profile, memeswap_set_wallet_refs, memeswap_create_credential) cover the very actions it lists. Without that distinction an agent cannot reliably tell this tool apart from its siblings.

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 explicit statement of when to call this tool versus the sibling tools it references, nor any indication of ordering (e.g. 'call this first before creating credentials'). Usage is only implied by the word 'onboarding'; nothing is stated about alternatives or exclusions.

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