Get HoodGrow Base B20 token registry

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

Beyond the readOnlyHint and other annotations, the description discloses a wealth of behavioral context: refresh cadence (every 4 hours), data source (directly from token contracts), pricing ($0.05 via x402, free with API key), and the exact condition for status flips (totalSupply() > 0). This goes well beyond what annotations provide.

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?

The description is structured with a lead purpose statement, a prominent PRE-LAUNCH warning, and concise operational details. Every sentence earns its place, covering purpose, caveats, cost, and refresh policy without redundancy.

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 bears full responsibility for explaining the tool's behavior. It covers return content (metadata, liveness), the pre-launch caveat, refresh policy, and cost, making it complete for an agent to decide on invocation.

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 has zero parameters, so the baseline is 4. The description adds no parameter-specific details, but none are needed; it focuses on the registry's contents and behavior, which is appropriate for an empty input schema.

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 clearly identifies the tool as a registry for Base mainnet B20 tokens, listing specific metadata fields (symbol, name, decimals) and a liveness signal. It distinguishes itself from sibling tools like get_token by focusing on the fixed B20 set and on-chain verification, making its purpose unambiguous.

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?

The description provides clear context for when to use the tool (when needing the B20 token registry on Base) and includes a critical usage warning about pre-launch tokens not being tradable. However, it does not explicitly mention alternatives or state when not to use it, so it lacks direct exclusions.

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