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

Annotations already declare it is not read-only, is open-world, and is non-idempotent, so the description need not restate safety. It adds real value by disclosing the return payload {social, profile, badge} and clarifying that social is the cookie consumed by downstream Squads tools — critical since no output schema exists. It still omits auth/rate-limit behavior beyond the session param.

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 dense sentence front-loads the usage and endpoint, then the return shape. It earns most of its words, though packing the endpoint, return object, and cookie explanation into one line makes it slightly dense rather than optimally scannable.

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 login/cookie-establishment call with no output schema, the description supplies the return fields and the downstream role of the social cookie, which is the key information an agent needs. Minor gaps remain around what profile/badge contain and any sequencing failure modes, but it is largely complete.

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%, and the schema already documents address, chainId, and session (including its origin in memeswap_session_open and non-storage guarantee). The description only reinforces the session bearer usage, adding no new parameter syntax or format detail, so the baseline 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?

States a specific verb (sign in) and resource (Squads) plus the exact endpoint (POST /api/social/login/wallet-session), so the agent knows precisely what the call does. It is also distinguishable from the related memeswap_session_open, which opens the wallet session this tool consumes.

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 says to use it with a session bearer and positions the output (social cookie) as the prerequisite for 'every Squads tool', implying correct sequencing. However, it never states when NOT to use it or names the specific alternative flow to follow if login is unnecessary.

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