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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds domain behavior the annotations cannot: what the signals mean and that results come back in each exchange's native market symbol format. Return shape and volume/pagination are not described, but with no output schema that is a minor gap.

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 purpose is front-loaded in the opening clause, and the four-case enumeration is compact rather than repetitive. It is a dense single sentence plus a tail clause; every element is informative, though the enumeration could be tightened.

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?

For a two-optional-parameter read tool with annotations and no output schema, the description covers what is returned (exchanges, coins, markets, counts) and the meaning of the signal. Only the exact result shape and result size are left unstated.

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 100%, so a baseline of 3 applies, but the description adds genuine meaning by explaining how coin and exchange compose as filters and what each combination returns. It stops short of restating accepted value formats (name vs key), which the schema already handles.

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 and scope: exchange markets on Cryptohopper that receive the daily trend signals, and it clarifies the signal semantics (buy when a coin turns long, sell when it turns flat). Combined with the market-format examples (BTCUSDT, XBT/EUR, BTC-USD), an agent can tell this apart from get_coin_signal or list_coins_and_venues without opening a schema.

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?

It spells out all four argument cases explicitly (no args = all exchanges with counts, exchange only, coin only, both), which is real selection guidance. It does not name a sibling alternative or an exclusion case, so it falls short of a 5.

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