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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description's one genuinely additive behavioral signal is 'Pro.', which hints at a subscription/tier gate, but it does not state what gets returned or any limits beyond the schema's max.

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 short sentences, ranking concept front-loaded, no filler. The dangling 'Pro.' fragment is slightly abrupt but costs almost nothing in length.

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 read-only ranking tool with no output schema and complete annotations, the description covers purpose and a use case, but leaves the dte semantics and expected return shape unexplained, so it is only minimally adequate.

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 coverage is only 50%, and the uncovered parameter is the dte enum ('all', 'lt8', 'gte8') whose meaning is opaque. The description does not compensate by explaining what these buckets mean or how dte and limit interact with the ranking.

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 verb and resource: tickers ranked by day-over-day change in total options open interest, with sub-modes (gainers, losers, most active). This distinguishes it from oi_timeseries (a time series) well enough, though it never names the sibling explicitly.

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 gives a use case ('where is new options positioning building?'), which implies when to reach for this tool, but offers no when-not guidance and names no alternative among the many sibling ranking tools (e.g., volatility_movers).

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