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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description goes beyond that by disclosing the score's weighting model (45/55 split) and the return payload (verdict, price, RSI), which helps the agent trust and interpret results. It doesn't mention auth, rate limits, or behavior for unknown coins.

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 no filler; the score definition and composition are front-loaded, and the interpretive caveat is a single well-placed clause. Every sentence earns its place.

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 usefully enumerates the return fields and the score's internal weighting. However, it leaves the coin identifier format unresolved and says nothing about error behavior for invalid or unknown coins, so it is adequate but not fully self-contained for a single-parameter lookup.

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?

There is one required parameter, 'coin', with 0% schema description coverage, so the description carries the full burden. It says only 'for a coin' and never specifies the expected identifier format (ticker symbol, CoinGecko id, or name). That ambiguity is a real invocation risk that the description fails to resolve.

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 resource ('OwlChart's 0 to 100 score for a coin') and states exactly what composes it (market regime 45%, entry signal 55%) plus the accompanying verdict, price and RSI. An agent can tell this is a proprietary composite-score lookup rather than raw market data. It stops short of explicitly contrasting itself with the sibling data feeds (get_price_history, get_funding_rates, etc.).

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: 'A reading of conditions, not a trade call' tells the agent how to interpret the output, which is a useful framing hint. But there is no statement of when to reach for this over a sibling like get_market_radar or scan_patterns, and no exclusion or prerequisite conditions.

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