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

Annotations already establish the safe read-only/idempotent profile, and the description adds substantial non-obvious behavior: rows with missing values and days_to_cover capped at 999.99 (dtc_capped true, days_to_cover null) are always listed last regardless of direction, thin stocks are filtered by default, there is no short-interest-as-%-of-float, and results are capped at 200 rows requiring paging.

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 core purpose, default ordering and the pagination cap are front-loaded, and most sentences carry unique information (cadence, null ordering, absence of %-of-float). It is a single dense paragraph that could be broken into shorter units, but there is little 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?

With an output schema present, return values need not be re-explained, and the description still covers row contents, the recent_settlement_dates companion field, edge-case ordering, volume filtering and page limits. For a 6-parameter, paginated ranking tool this leaves nothing an agent needs missing.

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 the baseline is 3, but the description adds interpretation beyond the schema: the cross-parameter interaction of dir=asc with sort=change ('largest decreases (covering)'), the reason min_avg_volume exists, and the twice-monthly, ~8-business-day reporting cadence that governs settlement_date.

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 states a precise verb and resource ('Every stock's FINRA short interest for one settlement date ... ranked like livermore.club/en/shorts'), including the ranking dimension and scope, which clearly separates it from the single-company get_short_interest sibling. An agent can tell what the tool returns and how it is ordered without opening the 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 explains when the defaults are appropriate ('default: the latest' settlement date, default sort=change) and gives a concrete use signal ('dir=asc gives the largest decreases (covering)'), plus the rationale for min_avg_volume. It does not, however, explicitly name when to choose this over get_short_interest, so there is no hard exclusion or alternative routing.

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