crypto_fear_greed

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies read-only access, the description lacks specifics on what the index measures (sentiment), its numeric scale (0-100), data source, update frequency, or caching behavior.

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 single sentence is appropriately sized for a zero-parameter tool, front-loaded with the action verb, and contains no redundant or 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?

While adequate for a simple retrieval tool with no parameters, the description lacks context about what the Fear & Greed Index represents (extreme fear to extreme greed sentiment scale) that would help an agent interpret results without an output schema or 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 input schema contains zero parameters, triggering the baseline score of 4. The description correctly implies no arguments are needed by referring to 'the current' index as a singular global value, requiring no further qualification.

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 uses a specific verb ('Get') and identifies the exact resource ('Crypto Fear & Greed Index'), making the purpose clear. However, it does not explicitly differentiate from sibling tools like 'crypto_market_overview' that might provide similar sentiment data.

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?

No guidance provided on when to use this tool versus alternatives like 'crypto_market_overview' or 'crypto_trending', nor are there any stated prerequisites or constraints for the zero-parameter call.

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