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

With no annotations available, the description carries the full burden and does so well: 'Read only', 'It pays nothing and promises no income', and the clarification that unlock checks 'are Worker/site checks, not on chain'. It also explains that a Disk is 'counted once', which prevents double-counting assumptions. It omits any statement about response shape beyond the field list or about leaderboard ordering/pagination.

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 front-loaded with the core concept, and the density is mostly justified by the scoring rules. However, the single run-on sentence with nested parentheses and semicolons is hard to parse, and the tier thresholds are effectively stated twice (once as a ladder, once inside the unlock requirements), adding length without new information.

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 two-optional-parameter, no-output-schema read tool, the description supplies the scoring formula, tier cut-offs, unlock thresholds, read-only nature, and the fields returned for a wallet. The remaining gap is the leaderboard entry shape and ordering, which an agent would have to discover at runtime.

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 100%, so the baseline is 3; the description adds above that by explaining exactly what supplying `wallet` yields (score, tier, parts, rank, unlocks) and what the invariants are (a Disk counted once). `limit` is only covered by the schema ('Board length, 1 to 100 (default 25)'), not the description, which keeps it from a 5.

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 defines the resource precisely: an estate 'STANDING' score computed from wallet holdings, plus an Estate leaderboard, with an explicit scoring formula and tier ladder. It distinguishes itself from the neighboring Rep system ('it only ranks wallets, next to Rep'), though it never names a sibling tool directly. An agent can tell what this returns without opening the schema.

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 clearly explains the two modes: 'Pass a wallet for its score, tier, parts, rank and what it unlocks' versus omitting it for the board. It also sets expectations negatively ('It pays nothing and promises no income'), which prevents misuse as an income tool. It does not explicitly name alternatives like reputation or get_estate_boost, so it falls short of a full when-to-use/when-not map.

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