get_cnn_fear_greed_index

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

No annotations are provided, so the description carries the full burden. It explains the scale (0=extreme fear, 100=extreme greed) and enumerates the seven indicators, but does not disclose side effects, network dependencies, 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 description is two sentences: the first defines the tool and its components, the second provides usage guidance. No redundant words, front-loaded with key information.

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 simple data retrieval tool with one parameter and no output schema, the description covers purpose, components, and usage. However, it lacks details about the output format, which would enhance completeness.

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 schema already describes the 'indicators' parameter with a clear description and default. The tool description does not add meaning beyond the schema; it mentions the indicators in general but not how to specify them via the parameter.

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 explicitly states the tool retrieves CNN's Fear & Greed Index with a 0-100 scale and lists seven specific indicators. It distinguishes from sibling 'get_crypto_fear_greed_index' by specifying 'stock market sentiment'.

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 includes a clear directive: 'Use this when asked about...' with specific scenarios like market sentiment and investor psychology. It provides context but does not mention exclusions or alternatives.

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