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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered; the description adds genuinely new context beyond that, namely the required API key or wallet token transmitted as X-API-Key or Authorization: Bearer, and the fact that the index is derived from the trailing 24h of scored articles.

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 tight sentences with the metric, range, scope and time window front-loaded, followed by the auth prerequisite. Nothing is redundant or padded.

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 and no parameters, the description carries the burden of describing the return value and does so at a high level (0-100 overall plus per vertical). It stops short of saying how the per-vertical breakdown is shaped or how it is framed as a result, which is the only remaining gap for a no-arg read 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?

The tool takes zero parameters and the schema is empty, so there is nothing to disambiguate; the baseline for a parameterless tool is 4, and the description adds no conflicting parameter claims.

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 names a specific metric (0-100 Fear & Greed index), its scope (overall and per vertical) and its computation window (last 24h of scored articles), so an agent knows exactly what it returns. It does not explicitly distinguish itself from the sibling muhabbit_sentiment_signals, but the defined resource is concrete enough to tell them apart.

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?

Usage is only implied: an agent can infer this is the tool for a market-sentiment readout, but the description never says when to prefer it over muhabbit_sentiment_signals, muhabbit_confidence or muhabbit_ticker_summary, nor any exclusion conditions.

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