Crypto Price ($0.01)

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

Discloses cost ($0.01 USDC on Base), which is important for an agent to know. No annotations exist, so description carries full burden. Lacks details on rate limits, payment failure handling, or response format.

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?

One efficient sentence plus a cost note. Every part is valuable and front-loaded.

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?

Covers purpose and cost, but missing output format, coin availability, and confirmation of real-time nature. Adequate for a simple one-param tool.

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?

Only one parameter (symbol) with schema description 'Coin symbol, e.g. eth' covering 100% schema. Description adds no extra meaning beyond the 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?

Clearly states it provides live crypto price, 24h change, market cap, and volume for any coin. Distinguishes from siblings like crypto_market, crypto_movers, and crypto_trending by specifying the exact data points.

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?

Mentions 'for trading agents' as a use case, implying the tool is intended for trading scenarios. However, it does not provide explicit guidance on when not to use it or alternatives among sibling tools.

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