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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is not needed for that. It earns credit by adding genuine domain context an agent cannot infer from structured fields: the metric reflects market-maker hedging rather than short interest, and the window is a rolling ~60 trading days. It still omits any statement about output volume or ties.

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?

Dense but front-loaded: the resource and metric come first, the interpretive caveat and the licensing link trail behind. Every clause carries information, though the FINRA terms URL is a marginal addition for an agent.

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 zero-parameter, read-only tool with no output schema, the description is adequate: it names the ranking, the window, the companion dataset, and the key interpretive limitation. It stops short of describing result size or ordering guarantees, but nothing needed to invoke it is 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?

The tool takes zero parameters and the schema is trivially empty, so there is nothing for the description to document. Baseline for a no-parameter tool applies.

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?

States a specific operation (rank the most-shorted liquid stocks), the ranking metric (average short % of volume), and the scope (rolling ~60 trading days), which is far more than the title conveys. It partially disambiguates from the short_interest_* siblings by noting short volume is 'not short interest,' but it never explicitly separates itself from short_volume_search or short_squeeze_candidates.

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 rather than stated: 'Pairs with fails-to-deliver for the short-selling picture' points at a companion tool, and the caveat warns the metric isn't short interest. There is no explicit when-to-use vs when-not guidance, nor any routing to the several closely-named sibling tools (short_volume_search, short_squeeze_candidates).

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