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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description still adds real context: the data source (FINRA), the bi-weekly settlement cadence, the days-to-cover field, and the "Pro" tier requirement, which signals an access/plan prerequisite not encoded anywhere else.

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?

Three compact sentences with no waste, front-loading the data source and scope before the example use case. Every sentence earns its place.

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?

With no output schema, the description does well by naming the returned content (short interest history plus days to cover). It stops short of describing the return shape or pagination for the limit parameter, but for a two-parameter read-only tool with full annotation coverage it is largely complete.

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 ticker and limit are fully documented in the schema, giving a baseline of 3. The description adds nothing about parameter format or defaults beyond what the schema already provides.

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 resource (FINRA short interest history) with a clear cadence (bi-weekly settlements) and a distinguishing metric (days to cover). It is distinguishable from the sibling short_volume, but it never names or contrasts that sibling explicitly, so it stops short of full 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 example query "how heavily shorted is GME?" implies the use case, which is genuinely helpful for routing. However there is no when-not-to-use guidance and no explicit reference to alternatives like short_volume, so usage is only implied rather than stated.

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