get_top_movers

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

With no annotations provided, the description carries the disclosure burden. It explains the temporal window ('Today's'), the ranking concept ('top'), and the filtering dimensions. It does not specify the exact ordering basis, return fields, or pagination behavior, but core behavior is reasonably transparent.

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 description is a single dense sentence with the purpose front-loaded and parameter options compactly listed in pipe notation. Every word earns its place with no filler or repetition.

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?

This is a simple all-optional, read-only list tool, and the description covers its core behavior and accepted inputs well. No output schema exists, so an exact return format would be useful, but an agent can infer the result is a ranked list of securities; the gaps are minor.

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 0%, so the description meaningfully compensates by defining valid values for index and direction. Two of the three parameters gain semantics beyond the bare schema; limit remains undocumented but has a clear default and intuitive meaning.

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 states a specific purpose: retrieving today's top gainers or losers. It clearly names the resource type and scope, though it doesn't explicitly differentiate from siblings like get_most_active or screen_stocks.

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 provides concrete input context by enumerating supported values for index and direction, which implies when the tool should be used. However, it does not mention alternatives, exclusions, or compare itself to similar tools such as get_most_active.

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