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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them: the FINRA data source, the bi-monthly settlement cadence (freshness), and the true-short-interest vs short-volume distinction. It does not disclose rate limits or output shape, but the source/cadence disclosure is substantive.

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 definition and the ranking criteria are front-loaded, and every sentence carries content. The trailing FINRA terms-of-use URL is compliance boilerplate that consumes space without helping an agent decide or invoke, keeping it short of a 5.

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 parameterless, read-only, no-output-schema tool, the description covers what data is returned, from where, and how often it refreshes. The one gap is that it does not say how many securities are ranked or how the two rankings are combined, which the agent would otherwise have to discover empirically.

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 per the rubric the baseline is 4. There is nothing for the description to clarify beyond confirming this is a parameterless snapshot query.

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 dataset (FINRA equity short interest), the two ranking dimensions (days-to-cover and largest absolute short positions), and the settlement vintage. It also distinguishes itself from the short-volume family with 'TRUE short interest (not short volume)'. However, it never disambiguates against the sibling short_squeeze_candidates, which appears to cover the same use case.

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?

'Use to find squeeze candidates and the most-shorted stocks' gives positive usage context, but there are no when-not conditions and no routing to the obvious alternatives (short_squeeze_candidates, short_interest_search, short_volume_most_shorted). The agent must infer which of the four short-interest tools to call.

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