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 discloses the data source (7-factor composite index), caching (5-min cache), and DB-backed storage. It implies read-only data retrieval but does not explicitly state safety; the nature of the tool (historical data query) makes that implicit.

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 relatively concise but contains some redundancy (e.g., repeating 'daily historical Fear & Greed score and classification'). It front-loads key information (score range, label) and is well-structured with a dash for sibling note.

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?

With no output schema, the description explains the return format (score and label per day) and data source. It mentions applicability for trend analysis and AI context. However, it lacks precise details on the JSON structure or sample output, 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 coverage is 100%, but the description states 'max 180 days' while the input schema's 'maximum' field is 90, an inconsistency that misleads the agent. The description adds minimal value over the schema, and the contradictory range undermines reliability.

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 clearly states the tool retrieves daily Fear & Greed score history with score and label per day for up to 180 days. It distinguishes itself from sibling 'fear_greed_monthly' by directing users to that tool for 2-year trends, ensuring the purpose is specific and unique.

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 explicitly advises using 'fear_greed_monthly' for longer-term analysis (2-year trends), indicating when not to use this tool. It also mentions default and maximum days, providing clear usage context. However, it does not exhaustively list all alternatives.

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