getBiggestGainers

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description adds almost nothing behavioral: no market/exchange coverage, no data recency or refresh cadence, no indication of how many symbols are returned or whether the ranking is intraday or end-of-day. 'Offering potential growth opportunities' is promotional rather than informational.

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 first sentence is front-loaded and does the real work. The second sentence largely restates 'largest price increases' as 'significant price surges' and closes with marketing language ('potential growth opportunities') that adds no decision-relevant information.

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 no-parameter read-only list tool the bar is low and annotations plus the name carry most of it. Still, an agent cannot tell from this definition what universe is ranked or how fresh the data is, which are the two facts that would determine whether to call it instead of the losers/actives/screener siblings.

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?

The tool takes zero parameters, which is the baseline-4 case since there is nothing for the description to disambiguate in the schema. The only residual gap is that the description does not state the market scope of the ranking (e.g. US equities only), which matters for a no-argument tool.

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 names a specific resource and outcome: stocks with the largest price increases / 'Top Stock Gainers'. An agent can tell this is a top-gainers list rather than a quote or screener call. It never names the obvious counterpart getBiggestLosers, so the sibling distinction is left to the tool name rather than the prose.

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 explicit when-to-use guidance and no exclusions. The description does not say how this differs from getBiggestLosers, getMostActiveStocks, or stockScreener, all of which could plausibly be selected for a similar 'what's moving' request. Only the implied framing ('leading the market') hints at usage.

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