Wallet reputation (free)

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds real value on top by stating it is free, that it works for any address on one specific chain, and exactly which datasets (deployer counts/score, off-market supply acquisition, realized WETH, insider rank) come back. It stops short of noting rate limits, latency, or behavior for unknown/EOA addresses.

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?

Two sentences, front-loaded with the value proposition and free/scope qualifier before the detail dump. The main sentence is dense with nested parentheticals but every clause carries distinct payload; only the closing tagline is arguably optional.

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 carries the return-value burden and does so thoroughly — it enumerates both result blocks and their subfields (counts, 0-100 score, WETH realized, insider ranking). For a one-parameter read tool, an agent has everything it needs to call this correctly.

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% with a single documented 'address' parameter, so the baseline is 3. The description earns one point above baseline by constraining the domain to Robinhood Chain addresses, which is a scoping fact the schema's generic '0x… wallet address' does not convey.

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?

Specific verb+resource+scope: 'Free wallet reputation for ANY Robinhood Chain address' that returns a deployer record (launched/real/dead + 0-100 score) and insider-flow history. The closing tagline 'The "who is this wallet" call' sharpens the intent. It does not name a sibling, so an agent must infer the boundary against robinx_deployer, robinx_caller, and robinx_entity.

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?

'For ANY Robinhood Chain address' gives a clear coverage condition and the tagline implies the wallet-lookup use case, but there is no explicit when-to-use-vs-alternative guidance. Nothing tells the agent when to prefer robinx_deployer, robinx_entity, or robinx_caller over this tool, despite obvious topical overlap.

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