Get HoodGrow token catalog

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

Description adds substantial behavioral detail beyond annotations: no API key or payment, doesn't consume daily units, prices read directly from Chainlink on-chain (not relayed), refresh interval of 15 minutes, observedAt field for age, priceSource for fallback logic, and corporate-action adjusted supply explanation. No contradiction with readOnly/idempotent/openWorld hints.

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?

Though lengthy, every sentence adds value—covering scope, return data, pricing mechanism, freshness, and edge cases. It is front-loaded with the core purpose and progressively details specifics, with no wasted words.

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?

Given no output schema, the description thoroughly explains what the response includes (symbol, name, contract address, live price, priceSource, 24h change, adjusted supply, corporate actions) and clarifies snapshot semantics (observedAt). It compensates fully for missing structured output documentation.

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 there is nothing to document. Baseline for 0 params is 4, and description correctly omits parameter details since none exist.

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?

Description explicitly states 'Free catalog and live price feed for all Robinhood Chain stock tokens' with specific resources (symbol, name, contract address, live price, etc.). Distinguishes from siblings by noting it lacks per-token DeFi depth and referencing get_token/get_defi for that.

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?

Clearly states use cases: 'Use for token discovery, spot prices, and tracking market movers.' Also explicitly mentions what it does NOT do (no DeFi depth) and points to alternative tools, providing unambiguous when-to-use guidance.

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