hyperd.token.info

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

No annotations provided; description mentions cost ($0.01 in USDC) but does not disclose other behavioral traits such as rate limits, authentication requirements, or whether it is read-only. Partial transparency.

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?

Two sentences, both highly informative: first states purpose and data, second adds value proposition and cost. No fluff.

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 enumerates returned data fields. For a simple parameter set (3 optional params, no enums, no nested objects), the description is fully sufficient.

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 coverage is 100% and description adds examples and clarifies the relationship between query, contract, and chain. Explains that query accepts symbol, name, or coingecko id, and that contract is an alternative.

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?

Clearly states verb 'Get aggregated token metadata' and lists specific data fields (market cap, supply, contract addresses, recent volume). Distinguishes from sibling tools by noting it replaces multiple lookups from CoinGecko, Etherscan, DefiLlama.

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?

Implies usage to replace multiple lookups but does not explicitly state when to use this tool versus siblings like hyperd.token.security or hyperd.pricing.get. No explicit when-not-to-use guidance.

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