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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the base rate (meta.early_base_rate) accompanies every rate, records are timing facts rather than forecasts, and wallets can vanish from the feed for spraying, underperforming, or silence. The last point is important because it tells the agent the list is dynamic and not a stable set.

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?

Three sentences, front-loaded with the selection criteria, then the interpretation rule, then the removal policy. Dense but each sentence carries distinct information; there is no filler.

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?

No output schema exists, so the description should carry the return-shape burden; it usefully names the meta.early_base_rate field but says nothing about record fields beyond the rate. Combined with two unexplained parameters, an agent can invoke it but cannot predict the payload well.

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% and neither 'limit' nor 'window' is explained in the description; 'early window' hints at a time concept but never ties it to the window parameter or its '30d' default, nor does it state that limit caps rows. With two undocumented parameters the description fails to compensate.

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 states a specific resource and a non-trivial selection criterion: Robinhood Chain wallets whose first buy fell in the early window of tokens that later crossed $100K. That is far more than a restatement of the name. It does not, however, explicitly distinguish itself from siblings like sol_early_wallets or rh_whale_wallets, so an agent must infer the chain/behavior boundary.

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?

There is no when-to-use guidance and no named alternative; the description never says to prefer this over rh_wallet_record or sol_early_wallets. The interpretive rule ('quote a wallet's rate only with the base rate') is about reading results, not about selecting the tool, so it doesn't satisfy this dimension.

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