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

No annotations are present, so the description carries the full behavioral burden. It usefully discloses the data source, the since-2022 coverage, the threshold rule, and the default of the newest date. However, it does not explain the return shape, how the two markets are combined, or how a symbol-specific query behaves beyond 'days on the list.'

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 compact and front-loads the definition before the usage modes. The second sentence is slightly telegraphic, but every clause adds signal and there is no 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?

For an optional-parameter read tool with no output schema, the description conveys the core data semantics and main invocation modes. It remains incomplete about the output format, limit behavior, and the exact request semantics for a symbol's days on the list, leaving some invocation details to inference.

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?

With schema description coverage at 50%, the description adds meaning to date ('default the newest'), symbol ('days on the list'), and market ('one listing market'). It says nothing about the `limit` parameter, which also lacks a schema description, so a quarter of the parameters remain unexplained.

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 identifies the resource precisely: Reg SHO threshold lists from Nasdaq and Cboe daily files, with a clear definition of the covered securities. It distinguishes itself from sibling tools like fails_to_deliver and short_interest through the five-settlement-day threshold rule, though it lacks an explicit imperative verb like 'retrieve' or 'list'.

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 implies usage through query modes ('One date, one symbol's days, or one listing market') but gives no guidance on when to choose this tool over siblings such as fails_to_deliver or short_interest. There are no explicit alternatives, exclusions, or decision rules.

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