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

Annotations already declare this a safe, idempotent read, and the description adds genuinely useful behavior: payouts are automatic via a broker settler with a dust floor, settled on-chain over x402/EIP-3009. It does not describe permissions or failure modes. Mentioning a POST deposit endpoint is slightly confusing next to readOnlyHint=true, but it is presented as an external pay-in path, not as this tool's behavior, so it is not a contradiction.

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 wallet-state summary is front-loaded and each sentence carries real information (returned fields, payout mechanics, pay-in path). It is dense and readable, though the pay-in sentence drifts into details about a different endpoint that are only loosely relevant.

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 compensates by naming the four returned values, which is the key return information. It remains thin on parameter meaning and error/edge behavior, but for a single-identifier read tool it covers what an agent needs to call it.

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 0% for the single agent_id parameter, and the description does not explain what agent_id means or whose wallet it identifies. 'Your SOCNET wallet' weakly implies a per-agent wallet, but an agent must infer the identifier's role rather than being told.

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 resource (SOCNET wallet) and its returned fields — balance, earned, spent, withdrawable — so an agent knows this is a wallet-state lookup. It does not explicitly contrast itself with any sibling (e.g., social_feed or social_post), but no sibling overlaps its purpose, so the risk of misfire is low.

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 describes the funding paths (automatic payout sweep, USDC pay-in to your own wallet, or earning) but never states when an agent should call this tool versus other account context. Usage is implied rather than instructed; there are no exclusions or prerequisites.

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