Get one HoodGrow token

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

Annotations already indicate read-only and idempotent behavior. The description adds substantial behavioral detail: price source (Chainlink on-chain), refresh rate (15 minutes), supply adjustment mechanism (ERC-8056), fallback behavior (priceSource), and failure on unknown symbols. No contradictions.

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 longer than average but every sentence provides essential information (cost, failure, price source, freshness, supply adjustment). It is front-loaded with the core purpose and then details. While verbose, it remains tightly organized with 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?

Despite no output schema, the description explains key return fields (observedAt, priceSource) and critical nuances (corporate-action adjustment, refresh cadence, source). It also discloses cost and failure behavior, making it complete for an agent to select and invoke the tool 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 covers 100% of the single parameter 'symbol' with a clear description including case-insensitivity. The description does not add additional parameter meaning beyond the schema, but it does mention failure on unknown symbols, which is behavioral rather than semantic. Baseline 3 is appropriate.

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 states the tool returns live price, corporate-action adjusted supply, DeFi depth, and corporate actions for a single token by symbol. It explicitly distinguishes itself from the free catalog by mentioning DeFi depth, making it unique among siblings.

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 notes the cost model (x402 or free API key) and differentiates from the catalog, but does not explicitly mention when to prefer other sibling tools like get_corporate_actions or get_defi. It provides context for its use case without explicit exclusions.

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