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

The readOnlyHint=true annotation already establishes this as a safe read, so the bar is lower. The description usefully adds that data originates from the SEC and refreshes only semi-monthly, which matters for staleness, but says nothing about coverage, pagination, or tier limits beyond what the schema states.

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?

A single dense sentence with zero filler, front-loading the definition of the dataset. It is appropriately sized for a two-parameter lookup tool, though it could spend one clause on the ticker-keyed access pattern.

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 simple read tool with 100% schema coverage and a readOnly annotation, most of what an agent needs is present. Still missing is the fact that the call is scoped to a single ticker and the implication that reported failures lag settlement by the publication cadence.

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%: ticker and limit are both fully documented, including the free-tier restriction on limit. The description adds no parameter-level meaning beyond that, so the baseline of 3 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?

The description explains the underlying dataset precisely: shares that failed to settle on the contractual settlement date, sourced semi-monthly from the SEC. That is clearer than restating the name, but it never states the retrieval action or that results are keyed by ticker, and it does not distinguish this from related siblings such as getShortInterest or getShortVolume.

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?

There is no statement of when to reach for this tool versus the many other SEC/equity data siblings, and no prerequisites or exclusions. The cadence note ('semi-monthly') hints at freshness expectations but is not framed as usage guidance.

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