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

Annotations already establish readOnly/idempotent/openWorld, but the description adds genuinely useful behavior the annotations do not: the ranking is based on 'the latest delayed print,' and the payload includes rank change vs the prior session, the #1 streak, unranked names with reasons, methodology and asOf. The delayed-print disclosure is the kind of freshness caveat an agent needs before quoting numbers.

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?

Three dense sentences, front-loaded with the resource and ranked-by definition before the field inventory. It is information-packed rather than padded, though the middle sentence is long and reads as a payload dump; nothing is wasted, but it is not maximally scannable.

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 carries the return-value burden and does so thoroughly: it enumerates rank, rank change, dividend rate, frequency, next cash event, total return vs bitcoin, streak, unranked reasons, methodology and asOf. For a one-optional-param read tool, an agent has everything needed to call and interpret it.

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% and the single timeframe param is already documented in the schema, so the baseline is 3. The description goes slightly beyond by tying the parameter to its effect — the total-return comparison with bitcoin 'over the chosen timeframe' — clarifying that the enum window governs the BTC benchmark leg, not the yield calculation itself.

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 verb-and-resource (US-listed bitcoin-treasury perpetual preferreds ranked by effective yield) and even enumerates the covered tickers (STRF, STRC, STRK, STRD, SATA, SATS). That level of scoping lets an agent tell it apart from generic preferred/tresury siblings such as get_pref or get_treasuries 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?

Usage is implied — reach for this when you want a yield ranking of these instruments — but no sibling tool is named and no explicit when-not condition is given. The line 'A sort, not a recommendation' is a framing caveat rather than routing guidance, so the agent must infer the alternative (get_pref, get_treasuries) on its own.

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