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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that this is an aggregated technical output, but says nothing about scope of 'top' perps, count, or freshness of data.

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 with no filler; the scope qualifier ('top USDT perps') precedes the list of returned fields. It is efficient, though very terse given the absence of an output schema.

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 input params and no output schema, the description carries return-value burden and does name the key fields (score, RSI, MACD, funding, OI). What remains unclear — how many setups, what 'top' means, refresh cadence — are minor gaps for a zero-argument read-only screener.

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, so there is nothing for the description to disambiguate — baseline 4 applies. No misleading claims about inputs are made.

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 (scored trade setups across top USDT perps) and enumerates the composite signals returned (0-100 score, RSI, MACD, funding, OI), so an agent can tell this is a screening/ranking tool rather than a raw data fetch. It stops short of naming or contrasting any sibling (e.g., get_markets, get_funding), which is why it isn't a 5.

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?

There is no sentence about when to reach for this screener versus the individual indicators it aggregates (get_funding, get_open_interest, get_klines). No preconditions, no exclusions, no alternative routing — usage is left entirely to inference from the name.

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