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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the data provenance (FINRA/SEC), the composite methodology, and a licensing/advice disclaimer. It does not disclose data freshness, pagination, or coverage limits, so it adds moderate value but not rich behavioral detail.

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 sentence is well front-loaded and dense with defined terms, but roughly half the text is compliance boilerplate (relicensing, 'not investment advice', FINRA terms URL). Some disclaimers are legitimate, yet they dilute the signal an agent needs for tool selection. Efficient opening, cluttered tail.

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 ranking/screening tool with no output schema, the description explains the score construction and the min_score filter, which is useful. However, it omits what a returned record contains and any indication of data freshness or result ordering, so an agent cannot anticipate the response shape. Adequate but incomplete.

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 description coverage is 100%, so both limit and min_score are already documented with defaults and bounds in the schema. The description merely restates 'Optional min_score filter' and adds no syntax or semantics beyond that. Baseline 3 is correct when the schema carries parameter meaning.

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 output (ranked short-squeeze candidates) and defines the composite signal precisely — FINRA days-to-cover + short-sale volume % + SEC fails-to-deliver per symbol. This composite framing distinguishes it from sibling single-source tools like short_interest_squeeze or fails_to_deliver_top, though it never names those competitors explicitly. A clear verb+resource with only implicit sibling differentiation.

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?

The description gives no when-to-use guidance and never names an alternative, despite dense sibling overlap (short_interest_squeeze, short_volume_most_shorted, upcoming_sales_pressure). The only usage-adjacent line, 'Optional min_score filter,' is a parameter note rather than routing guidance. An agent must infer the relationship to neighboring tools on its own.

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