Get HoodGrow token catalog

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds meaningful behavioral context: it discloses the pricing model and the specific data included (e.g., best Morpho supply APY, Uniswap V3 TVL). This goes beyond the structured fields and helps the agent understand the tool's cost and scope.

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 two sentences: the first lists the catalog contents, the second states pricing and the preferred alternative. No redundant details, front-loaded with the core purpose, and every sentence earns its place.

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?

For a read-only, zero-parameter catalog tool with no output schema, the description fully conveys what the agent needs: the data returned, the cost, and the alternative for single symbols. It is complete given the tool's low complexity and rich annotations.

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 schema coverage is vacuously 100%. The description does not need to explain parameters; the baseline for 0-param tools is 4. It adds no parameter-specific info because 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?

The description clearly states the tool provides a full catalog of Robinhood Chain stock tokens with specific data types (live price, supply, DeFi depth, corporate actions). It distinguishes itself from siblings by explicitly mentioning 'prefer get_token for a single symbol' and covering corporate actions in bulk.

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 explicitly mentions when to use an alternative ('prefer get_token for a single symbol') and provides cost context (paid per call, free with API key), helping the agent decide between tools. The catalog nature implies use for multiple tokens, and the pricing guidance further informs when to avoid it.

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