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

With no annotations, the description carries the full burden, and it does disclose a genuinely useful behavioral trait: cost of 2 credits per call. However it says nothing about latency, rate limits, or that this is a strictly read-only lookup with no side effects, so the safety/behavior profile is only partly covered.

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?

A single front-loaded sentence: resource first, then the metric list, then cost. The metric enumeration is dense but each item earns its place since no output schema exists to communicate the return shape. No filler.

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?

Because there is no output schema, the enumerated metrics are important and usefully present, and cost is covered. But the days parameter's meaning remains unexplained and no sibling routing is given, leaving gaps for a tool whose whole value is the parameterized lookback window.

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?

Schema coverage is 50%: id is well documented with an example and a pointer to crypto_search, but days (default 180, range 30–365) has no description and the tool description never mentions it or that it controls the lookback window. The description therefore fails to compensate for the documented gap.

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?

States a specific resource ('one coin') and enumerates the exact analytics returned (price history, RSI, MAs, trend, volume, volatility, drawdown, headlines), which is far more concrete than a bare 'get coin data'. It implicitly separates itself from the multi-coin crypto_markets and news-only crypto_news, but never names a sibling to make the boundary explicit.

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 statement of when to use this versus crypto_markets, crypto_signals, or crypto_news, and no prerequisites. The only guidance ('use crypto_search if unsure') lives in the input schema's id description, not here. The cost line is the sole decision-relevant context.

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