TradingView-only: bitcoin pulse

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

No annotations are supplied, so the description carries the full behavioral burden. The one useful fact it adds is the data provenance ('Envelope labelled TRADINGVIEW'), but it never states that the call is read-only, whether it is rate-limited, or how fresh the data is. For a zero-parameter snapshot tool the risk is low, yet the disclosure remains thin.

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 text is short and front-loads the health summary, which is good. However, the 'Returns:' line is cryptic — 'Envelope labelled TRADINGVIEW' reads as internal implementation detail rather than something an agent can act on.

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?

An output schema exists, so the description need not explain return values, which lowers the bar. Still, for a composite market-health indicator the description leaves the meaning of 'dominance proxies' and 'trend' undefined, and gives no sense of scope (timeframe, spot vs. futures) that an agent would need to interpret the result.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description does not introduce confusing or phantom parameter-like language.

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 the resource (Bitcoin market health) and lists three metric families: trend, dominance proxies, volatility. That is more specific than a tautology, but the verb is implicit and 'dominance proxies' is vague. Nothing distinguishes it from crypto-focused siblings such as crypto_top_movers, crypto_bollinger_scan or crypto_multi_timeframe.

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 when-to-use or when-not-to-use guidance is given. With roughly ten crypto-adjacent siblings in the list, an agent has no stated basis for choosing this tool over crypto_multi_timeframe or crypto_top_movers, and no preconditions or exclusions are mentioned.

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