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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the meaningful temporal scope word 'daily', but says nothing about the hard cap of 10 results, ranking order, or whether the ranking is intraday vs. end-of-day.

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?

A single front-loaded sentence that enumerates the resource scope with zero filler. Nothing to trim and nothing buried.

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?

An output schema exists, so return-value documentation is not required. However, for a tool spanning eight ranking categories, the description gives no sense of what distinguishes them or of result-count behavior beyond the schema's maximum, leaving meaningful inference work to the agent.

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 listed mover types map cleanly onto the category enum, but the naming is not literal (description's 'activity' is the enum's 'most_active', 'gaps' covers both gap_up and gap_down), so it adds modest clarification. The limit parameter — bounded 1-10 with a default of 10 — is documented only by schema constraints and gets no semantic treatment in the description.

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 ('Get') and resource ('daily gainers, losers, activity, unusual volume, gaps or 52-week extremes'), which concretely enumerates what the tool returns. It is distinguishable from get_quotes or get_market_snapshot by focusing on ranked movers rather than raw prices, though it never names those siblings 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?

There is no explicit when-to-use guidance and no routing to alternatives such as get_market_overview, get_market_snapshot, or run_screener. Usage is only implied by the list of mover types; an agent must infer from the category list when this beats a screener or snapshot call.

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