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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds real value by disclosing the ordering (ranked by 24h change) and the semantic of tradeable_only, but says nothing about result freshness beyond "Today's", pagination, or return shape.

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?

Two short sentences with no filler; the ranking criterion is front-loaded and the filter is explained second. The tradeable_only clause slightly duplicates what the schema already says, which keeps it from a top score.

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 zero-required-parameter, read-only listing tool with full schema coverage and no output schema, the description covers purpose, ordering, and filtering. It could say more about what a returned mover entry contains, but the omission is minor at this complexity.

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 all three parameters are already documented in the schema, including the fact that only "change" works for `by`. The description reinforces this and glosses tradeable_only as "the ones you can buy now", which is a modest gain over the schema baseline.

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 (stock tokens on Robinhood Chain) and an explicit ranking criterion (the pool's 24h change), so the agent knows this is a movers/leaderboard listing rather than a single-quote lookup. It does not explicitly distinguish itself from siblings like stock_quote, but the purpose is unambiguous on its own terms.

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?

Usage is only implied: the ranking-by-24h-change framing suggests a screening use case, and the tradeable_only sentence hints at a buy-now filter. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for single-token lookups.

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