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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower, yet the description still adds real value: the HTTP method and path, the required Authorization: Bearer header, and the semantics of scope=profile. It does not describe pagination or the shape of the returned summary, which keeps it short of a 5.

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: purpose first, then endpoint/auth mechanics, then the scope nuance. Dense but every clause carries information; the semicolon-chained style is slightly run-on but not padded.

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 at least says it returns the server summary and names the two quantities (pending and available Earn amounts). Combined with the auth and scope details, an agent has enough to invoke it correctly, though the return format itself stays vague.

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 coverage is 67% and the undocumented parameter is scope, which the description does cover (scope=profile totals every wallet of the verified profile). It also confirms wallet is used as a query parameter; only the session parameter's meaning is left entirely to the schema, which already documents it well.

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 (read) and resource (pending and available Earn amounts for the session wallet), plus the underlying endpoint. It is clearly distinguishable from most siblings, but it never names the nearest neighbor, memeswap_earn_leaderboard, so the differentiation is inferred rather than stated.

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 to read ... for the session wallet" gives implied usage, and the scope=profile clause tells the agent about a per-profile aggregation mode. However there is no explicit when-not guidance and no routing to earn_leaderboard or portfolio for related questions, so usage is only partially covered.

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