crypto-fear-greed

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

No annotations given, so description carries full burden. It discloses read-only nature, data source (alternative.me), update frequency (daily), and cost ($0.005/call). No contradictions; behavior is clearly a data retrieval.

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, front-loaded with main output, then details on trend, summary, data source, and cost. Every sentence contributes information without redundancy.

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 simple tool with one parameter and no output schema, description fully covers expected output (score, trend, min/max/avg, regime signal), data source, update frequency, and pricing. No gaps for agent to infer.

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 already describes the single parameter 'days' with full coverage. Description adds value by explaining that it affects trend (7-day) and summary (30-day min/max/avg), linking parameter to output components.

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 clearly states the tool provides the Crypto Fear & Greed Index with current score, trend, min/max/avg, and trading regime signal. It distinguishes from generic crypto tools by specifying the index and included metrics.

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?

Description implies usage for market sentiment but does not explicitly state when to use this tool versus alternatives like crypto-momentum-pack or crypto-pulse. No exclusions or alternative suggestions provided.

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