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

With no annotations, the description must fully disclose behavioral traits. It mentions the data source and history window but omits important behaviors: it is read-only, but no explicit statement; it does not describe pagination, response format, error conditions, or data completeness. It also mentions 'limit' which does not exist in the schema, causing confusion. The absence of safety or side-effect disclosure is a gap.

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 description is two sentences and front-loads the core purpose, then describes modes. It is efficient with no filler. The only flaw is the avoidable 'limit' error, but from a conciseness standpoint, it is well-structured and readable.

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?

Given no output schema, the description should clarify what the tool returns. It mentions 'short sale volume and total volume per symbol' and 'short share', but does not explain the response structure, whether pagination exists, or what the default behavior is when no parameters are supplied. The two modes are described, but without detail on sorting, limits, or error handling. The 'limit' error also reduces trust. For a tool with 4 parameters and no annotations, this is insufficient.

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?

While schema coverage is 100%, the description incorrectly references a 'limit' parameter while the schema has 'days'. It does add context like 'oldest first' and 'up to 5,000 days', but the erroneous mention of 'limit' undermines the accuracy. The description adds moderate value but includes a misleading term, so it does not improve on the schema adequately.

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 resource (FINRA Reg SHO files), a specific metric (short sale volume, total volume, short share), and the time range (since August 2021). It clearly differentiates from siblings like short_interest by focusing on daily volume from Reg SHO. The purpose is unambiguous.

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 explains two distinct usage modes: historical data for a symbol (with window selection via 'from', 'to', and 'days') and the latest day's largest short volumes. It gives clear context on how to invoke each, though it does not explicitly contrast with alternative tools (e.g., short_interest, fails_to_deliver). Still, the in-tool usage guidance is strong.

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