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

The "Read-only" claim merely restates readOnlyHint and destructiveHint=false, earning no credit. Beyond annotations it adds two genuinely useful facts: the per-wallet auth scoping shared with get_my_vault, and the result-state model (earned / still open with remaining requirement / unread). It says nothing about ordering, size, or how "what is left to earn it" is represented.

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?

It is a single sentence with no filler, but it is overstuffed: the colon-and-parenthesis construction and the dangling list of criteria make the reader parse twice. Key information (per-wallet scope) is front-loaded, which helps, but the second half is dense to the point of obscurity.

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 and no parameters, the description carries the return-value burden, and it does describe the three result states plus the presence of remaining-to-earn detail. It falls short only on the ambiguous criteria list and the absence of any indication of result ordering or shape.

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 the schema has no semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameter talk and instead spends its words on scope and return content.

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 specific resource ("your badges") scoped to the signed-in wallet, which is clearer than the bare tool name. However, "badges" is never defined, and the trailing list ("holding time, claims, claimed amounts in real units, locking, the top 20 and voting") is syntactically ambiguous — it reads as either badge categories or input data, so the agent cannot form a crisp picture of what is returned.

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?

Scope is implied by "the wallet you signed in with" and the note that it uses the same sign-in as get_my_vault, which tells the agent this is a personal, authenticated read. There is no explicit when-to-use versus siblings such as get_my_claims or get_my_performance, and no statement of when not to call it.

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