Short interest

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

Annotations already declare readOnlyHint and openWorldHint, and the description usefully adds that access is free and requires no credential, plus which metrics are returned. It omits rate limits, reporting lag, or refresh cadence, so it stops short of full behavioral disclosure.

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 capability is front-loaded in the first sentence with the returned metrics in the second. The closing Schloss remark is interpretive padding, but it does convey how to weigh the output, so the length is defensible rather than wasteful.

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 single-parameter tool with no output schema, the description compensates by naming the returned metrics and the source of the data. What remains missing is freshness/lag information and any hint about error behavior for non-US tickers.

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% and the single ticker parameter is already documented there as case-insensitive with a max length. The description adds no syntax, format, or edge-case guidance beyond what the schema supplies, so baseline 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?

Names the specific source (FINRA consolidated short interest) and the exact scope (one ticker), and enumerates the reported fields: shares short, days to cover, and trend across the reporting window. No sibling tool covers short interest, and an agent can distinguish this from analyze_ticker or get_quotes immediately.

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 frames the data's interpretive role (a reason a name is cheap, not an automatic veto) but never states when to call the tool versus alternatives or what preconditions exist beyond one ticker. Usage is implied rather than directed.

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